{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90338 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90338 is a denial of service vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-90338 and fix it if it is affected.\n\nWhat it is: CVE-2026-90338 is a denial of service vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-90338 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-90338/ (Markdown: https://insights.sbomify.com/CVE-2026-90338/index.md)","id":"CVE-2026-90338","markdown":"https://insights.sbomify.com/CVE-2026-90338/index.md","name":"CVE-2026-90338","record":{"aliases":["BELL-CVE-2026-90338","DEBIAN-CVE-2026-90338","GHSA-hxcg-grxr-xv6j","UBUNTU-CVE-2026-90338"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel serial driver","requires_auth":"none","summary":"A Linux kernel bug in the PL011 serial driver causes a crash when printing logs in atomic contexts on PREEMPT_RT systems, leading to denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nserial: amba-pl011: keep console clock enabled for atomic writes\n\npl011_console_write_atomic() runs from nbcon atomic context, where\nsleeping is not allowed. It calls clk_enable(), which takes the common-clk\nenable_lock. Under PREEMPT_RT that is a sleeping lock:\nclk_enable_lock() first tries spin_trylock_irqsave(), but on contention\nfalls back to spin_lock_irqsave(). Therefore, an atomic-context printk on\nan RT kernel with a clk-backed pl011 can trip:\n\n  BUG: sleeping function called from invalid context at spinlock_rt.c:48\n    __might_resched from rt_spin_lock\n    rt_spin_lock from clk_enable_lock\n    clk_enable_lock from clk_enable\n    clk_enable from pl011_console_write_atomic\n    ... from vprintk_emit\n\nThis was found and reproduced on PREEMPT_RT. Arm32 and arm64 DT SoCs are\naffected; arm64 SBSA/ACPI has no clk, so clk_enable(NULL) short-circuits\nbefore the lock. In addition, write_atomic() may be invoked from NMI\ncontext and is documented to avoid locking. Removing clk_enable() from\nthe callback also avoids a potentially unsafe NMI acquisition of the\ncommon-clock enable_lock.\n\nAn nbcon atomic-capable console must be printable from any context, so\nthe clock cannot be gated between writes. Enable the clock while the\nconsole is available for output: use clk_prepare_enable() in\npl011_console_setup(), release it via clk_disable_unprepare() in the\nconsole .exit() callback, and drop the per-write clk_enable()/clk_disable()\npairs from write_atomic() and write_thread().\n\nWhen printk suspends consoles, drop the reference after\nuart_suspend_port() stops console access and restore it before\nuart_resume_port() -- but only if suspend actually marked the port\nsuspended (a wake-capable tty stays running and must keep its clock), and\nkeep it when console_suspend_enabled is false so no_console_suspend works.\n\nThe active power cost of keeping the clock enabled is platform-dependent:\nnone where the UART clock is a fixed always-on oscillator, real where it\nis a gateable clock branch, which then cannot be gated (nor possibly can\nits parent clocks) while the console is available for output. When serial\ncore actually suspends the port, the reference is released so the clock\nprovider can gate the clock tree.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"serial: amba-pl011: keep console clock enabled for atomic writes","id":"CVE-2026-90338","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"powerpc/syscall: Fix syscall skip handling for seccomp and ptrace","id":"CVE-2026-90339"},"packages":[],"prev":{"headline":"serial: core: do fallible allocations before the console can be registered","id":"CVE-2026-90337"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A Linux kernel bug in the PL011 serial driver causes a crash when printing logs in atomic contexts on PREEMPT_RT systems, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-90338/"}