UBUNTU-CVE-2026-90585

See a problem?
Please try reporting it to the source first.
Source
https://ubuntu.com/security/CVE-2026-90585
Import Source
https://github.com/canonical/ubuntu-security-notices/blob/main/osv/cve/2026/UBUNTU-CVE-2026-90585.json
JSON Data
https://api.osv.dev/v1/vulns/UBUNTU-CVE-2026-90585
Upstream
Published
2026-11-10T00:00:00Z
Modified
2026-11-11T09:41:40Z
Severity
  • 4.6 (Medium) CVSS_V3 - CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
  • Ubuntu - medium
Summary
[none]
Details

The Renesas RA SCI UART driver's receive-error ISR, uart_ra_sci_eri_isr() in drivers/serial/uart_renesas_ra_sci.c, acknowledged the error condition only when a Zephyr interrupt-driven callback had already been registered. With CONFIG_UART_INTERRUPT_DRIVEN=y and CONFIG_UART_ASYNC_API=n, if data->user_cb is NULL the ISR body is empty: the SCI error flags (SSR.ORER, SSR.FER, SSR.PER) are left set and the ICU event flag R_ICU->IELSR_b[eri_irq].IR is never cleared, so the interrupt re-pends immediately and the ISR is re-entered without end. The error interrupt is masked at boot by uart_ra_sci_init(), but FSP's R_SCI_UART_Open() unconditionally re-enables it, and uart_ra_sci_configure() - the back end of the public uart_configure() API, enabled by default via CONFIG_UART_USE_RUNTIME_CONFIGURE - performs a Close()/Open() pair without re-masking it. Any runtime uart_configure() therefore leaves the error interrupt live regardless of whether a callback has been set, as does calling uart_irq_err_enable() on its own. An instance used with the polling API, or the window between uart_configure() and uart_irq_callback_user_data_set(), thus runs with the error interrupt unmasked and no callback registered. The trigger is an ordinary receive line error - overrun, framing, parity, or a break condition - which is fully determined by the device attached to the serial link. A peer able to assert a break or transmit at a mismatched baud rate produces such an error at will, so a single frame is enough to enter the state. The impact is availability only: the CPU is captured in the re-entering ISR and never returns to thread context, hanging the entire system until an external reset or hardware watchdog fires. There is no memory corruption or information disclosure. Builds using the asynchronous UART API are unaffected, because the fall-through to FSP's sci_uart_eri_isr() clears both the error flags and the pending IRQ.

References

Affected packages

Ubuntu:16.04:LTS
zephyr

Package

Name
zephyr
Purl
pkg:deb/ubuntu/zephyr?arch=source&distro=xenial

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0 Unknown introduced version / All previous versions are affected

Affected versions

3.*
3.1.2-1
3.1.2-1build1

Ecosystem specific 

{
    "binaries": [
        {
            "binary_name": "libzephyr4",
            "binary_version": "3.1.2-1build1"
        },
        {
            "binary_name": "libzephyr4-krb5",
            "binary_version": "3.1.2-1build1"
        },
        {
            "binary_name": "zephyr-clients",
            "binary_version": "3.1.2-1build1"
        },
        {
            "binary_name": "zephyr-server",
            "binary_version": "3.1.2-1build1"
        },
        {
            "binary_name": "zephyr-server-krb5",
            "binary_version": "3.1.2-1build1"
        }
    ]
}

Database specific

source 
"https://github.com/canonical/ubuntu-security-notices/blob/main/osv/cve/2026/UBUNTU-CVE-2026-90585.json"
Ubuntu:18.04:LTS
zephyr

Package

Name
zephyr
Purl
pkg:deb/ubuntu/zephyr?arch=source&distro=bionic

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0 Unknown introduced version / All previous versions are affected

Affected versions

3.*
3.1.2-1build1
3.1.2-1build2

Ecosystem specific 

{
    "binaries": [
        {
            "binary_name": "libzephyr4",
            "binary_version": "3.1.2-1build2"
        },
        {
            "binary_name": "libzephyr4-krb5",
            "binary_version": "3.1.2-1build2"
        },
        {
            "binary_name": "zephyr-clients",
            "binary_version": "3.1.2-1build2"
        },
        {
            "binary_name": "zephyr-server",
            "binary_version": "3.1.2-1build2"
        },
        {
            "binary_name": "zephyr-server-krb5",
            "binary_version": "3.1.2-1build2"
        }
    ]
}

Database specific

source 
"https://github.com/canonical/ubuntu-security-notices/blob/main/osv/cve/2026/UBUNTU-CVE-2026-90585.json"
Ubuntu:20.04:LTS
zephyr

Package

Name
zephyr
Purl
pkg:deb/ubuntu/zephyr?arch=source&distro=focal

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0 Unknown introduced version / All previous versions are affected

Affected versions

3.*
3.1.2-1build3

Ecosystem specific 

{
    "binaries": [
        {
            "binary_name": "libzephyr4",
            "binary_version": "3.1.2-1build3"
        },
        {
            "binary_name": "libzephyr4-krb5",
            "binary_version": "3.1.2-1build3"
        },
        {
            "binary_name": "zephyr-clients",
            "binary_version": "3.1.2-1build3"
        },
        {
            "binary_name": "zephyr-server",
            "binary_version": "3.1.2-1build3"
        },
        {
            "binary_name": "zephyr-server-krb5",
            "binary_version": "3.1.2-1build3"
        }
    ]
}

Database specific

source 
"https://github.com/canonical/ubuntu-security-notices/blob/main/osv/cve/2026/UBUNTU-CVE-2026-90585.json"
Ubuntu:22.04:LTS
zephyr

Package

Name
zephyr
Purl
pkg:deb/ubuntu/zephyr?arch=source&distro=jammy

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0 Unknown introduced version / All previous versions are affected

Affected versions

3.*
3.1.2-1build3

Ecosystem specific 

{
    "binaries": [
        {
            "binary_name": "libzephyr4",
            "binary_version": "3.1.2-1build3"
        },
        {
            "binary_name": "libzephyr4-krb5",
            "binary_version": "3.1.2-1build3"
        },
        {
            "binary_name": "zephyr-clients",
            "binary_version": "3.1.2-1build3"
        },
        {
            "binary_name": "zephyr-server",
            "binary_version": "3.1.2-1build3"
        },
        {
            "binary_name": "zephyr-server-krb5",
            "binary_version": "3.1.2-1build3"
        }
    ]
}

Database specific

source 
"https://github.com/canonical/ubuntu-security-notices/blob/main/osv/cve/2026/UBUNTU-CVE-2026-90585.json"
Ubuntu:24.04:LTS
zephyr

Package

Name
zephyr
Purl
pkg:deb/ubuntu/zephyr?arch=source&distro=noble

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0 Unknown introduced version / All previous versions are affected

Affected versions

3.*
3.1.2-1.1
3.1.2-1.1build1

Ecosystem specific 

{
    "binaries": [
        {
            "binary_name": "libzephyr4",
            "binary_version": "3.1.2-1.1build1"
        },
        {
            "binary_name": "libzephyr4-krb5",
            "binary_version": "3.1.2-1.1build1"
        },
        {
            "binary_name": "zephyr-clients",
            "binary_version": "3.1.2-1.1build1"
        },
        {
            "binary_name": "zephyr-server",
            "binary_version": "3.1.2-1.1build1"
        },
        {
            "binary_name": "zephyr-server-krb5",
            "binary_version": "3.1.2-1.1build1"
        }
    ]
}

Database specific

source 
"https://github.com/canonical/ubuntu-security-notices/blob/main/osv/cve/2026/UBUNTU-CVE-2026-90585.json"
Ubuntu:26.04:LTS
zephyr

Package

Name
zephyr
Purl
pkg:deb/ubuntu/zephyr?arch=source&distro=resolute

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0 Unknown introduced version / All previous versions are affected

Affected versions

3.*
3.1.2-1.1build1
3.1.2-4

Ecosystem specific 

{
    "binaries": [
        {
            "binary_name": "libzephyr4",
            "binary_version": "3.1.2-4"
        },
        {
            "binary_name": "libzephyr4-krb5",
            "binary_version": "3.1.2-4"
        },
        {
            "binary_name": "zephyr-clients",
            "binary_version": "3.1.2-4"
        },
        {
            "binary_name": "zephyr-server",
            "binary_version": "3.1.2-4"
        },
        {
            "binary_name": "zephyr-server-krb5",
            "binary_version": "3.1.2-4"
        }
    ]
}

Database specific

source 
"https://github.com/canonical/ubuntu-security-notices/blob/main/osv/cve/2026/UBUNTU-CVE-2026-90585.json"
Ubuntu:26.10
zephyr

Package

Name
zephyr
Purl
pkg:deb/ubuntu/zephyr?arch=source&distro=stonking

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0 Unknown introduced version / All previous versions are affected

Affected versions

3.*
3.1.2-4

Ecosystem specific 

{
    "binaries": [
        {
            "binary_name": "libzephyr4",
            "binary_version": "3.1.2-4"
        },
        {
            "binary_name": "libzephyr4-krb5",
            "binary_version": "3.1.2-4"
        },
        {
            "binary_name": "zephyr-clients",
            "binary_version": "3.1.2-4"
        },
        {
            "binary_name": "zephyr-server",
            "binary_version": "3.1.2-4"
        },
        {
            "binary_name": "zephyr-server-krb5",
            "binary_version": "3.1.2-4"
        }
    ]
}

Database specific

source 
"https://github.com/canonical/ubuntu-security-notices/blob/main/osv/cve/2026/UBUNTU-CVE-2026-90585.json"