CVE-2026-80886serial: msm: Disable DMA for kernel console UART
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: serial: msm: Disable DMA for kernel console UART At the moment, concurrent writes from userspace and the kernel to the console can trigger a race condition that results in an infinite loop of the same messages printed over and over again. This is most likely to happen during system startup or shutdown when the init system starts/stops a large number of system services that interact with various kernel code. When userspace writes to the TTY device, the driver initiates an asynchronous DMA transfer and releases the port lock. At the same moment, the kernel printk path might grab the port lock and re-configure the UART controller for PIO, without waiting for the DMA operation to complete. It seems like this collision results in zero progress being reported for the DMA engine, so the same text is printed to the console over and over again. For the kernel console, we want a reliable output path that will be functional even during crashes etc. So rather than implementing complex code to synchronize the kernel console write routines with the userspace DMA write routines, simply disable DMA for the console UART instance. Similar checks exist in many other serial drivers, e.g. 8250_port.c, imx.c, sh-sci.c etc.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Sep 4, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 3a878c430fd6eb4f8587f9ebd187f773bf85d1d6 before f58e568dc308c8e13f7730c8de2da5ed514e540d; from 3a878c430fd6eb4f8587f9ebd187f773bf85d1d6 before bb4296de5b538b575978c588cb3738ab8524d01a; from 3a878c430fd6eb4f8587f9ebd187f773bf85d1d6 before 6acea62738ed4cae6746483026706a773b44dad7; from 3a878c430fd6eb4f8587f9ebd187f773bf85d1d6 before abc1926c88c189e5d698b91ed6890e09ab5c321d; from 3a878c430fd6eb4f8587f9ebd187f773bf85d1d6 before 2727744ccb5ca59090451451ee94f530b1be04a5; from 3a878c430fd6eb4f8587f9ebd187f773bf85d1d6 before d354716245192de2d203f2b35f22ab8dc13595e2; from 3a878c430fd6eb4f8587f9ebd187f773bf85d1d6 before e3b42e326f4f30efcdc90bad5f5ba37e1cd91a47; from 3a878c430fd6eb4f8587f9ebd187f773bf85d1d6 before 22dd2777e6c180e1c945b00f6d18550979436324 | CNA record |
References
- https://git.kernel.org/stable/c/f58e568dc308c8e13f7730c8de2da5ed514e540d
- https://git.kernel.org/stable/c/bb4296de5b538b575978c588cb3738ab8524d01a
- https://git.kernel.org/stable/c/6acea62738ed4cae6746483026706a773b44dad7
- https://git.kernel.org/stable/c/abc1926c88c189e5d698b91ed6890e09ab5c321d
- https://git.kernel.org/stable/c/2727744ccb5ca59090451451ee94f530b1be04a5
- https://git.kernel.org/stable/c/d354716245192de2d203f2b35f22ab8dc13595e2
- https://git.kernel.org/stable/c/e3b42e326f4f30efcdc90bad5f5ba37e1cd91a47
- https://git.kernel.org/stable/c/22dd2777e6c180e1c945b00f6d18550979436324
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.