Kernel crash via probe-time NULL dereference
Published Sep 3, 2026 · Updated Sep 3, 2026
NULL pointer dereference in Linux 5.1 and later causes a kernel crash if a Xilinx ASoC interrupt occurs during driver probe. The formatter PCM handlers call dev_get_drvdata() before probe stores the driver data, then pass the resulting NULL pointer to readl(). Exposure requires the Xilinx formatter device and an interrupt in the interval after IRQ registration but before probe completes; the documented consequence is a crash.
Summary
What happened
NULL pointer dereference in Linux 5.1 and later causes a kernel crash if a Xilinx ASoC interrupt occurs during driver probe. The formatter PCM handlers call dev_get_drvdata() before probe stores the driver data, then pass the resulting NULL pointer to readl(). Exposure requires the Xilinx formatter device and an interrupt in the interval after IRQ registration but before probe completes; the documented consequence is a crash.
The record
- CVE
- CVE-2026-80743
- Published
- Sep 3, 2026
- Updated
- Sep 3, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 3, 2026CVE publishedPublication date reported by the CVE source.
- Sep 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.1
- Affected versionversion=6f6c3c36f0917be24587eeba818ab4fdfcb5465a <09e4c486348e176c083f8bee9169ae8f408cf8d1
- Affected versionversion=6f6c3c36f0917be24587eeba818ab4fdfcb5465a <0d58a70b6dc7b65772e3ef7c43beb91882cf9ed5
- Affected versionversion=6f6c3c36f0917be24587eeba818ab4fdfcb5465a <721cfeb0b9572084435695ae535411b921d1ea68
- Affected versionversion=6f6c3c36f0917be24587eeba818ab4fdfcb5465a <7d857aec162fb02d10ce326aecc1ac7509c31f43
- Affected versionversion=6f6c3c36f0917be24587eeba818ab4fdfcb5465a <a85315f2eb06adc5597a7103e1910fc7d0d35ffd
- Affected versionversion=6f6c3c36f0917be24587eeba818ab4fdfcb5465a <b4ef887bee4d3c177adac5d1eab8b2de31b08ac3
- Affected versionversion=6f6c3c36f0917be24587eeba818ab4fdfcb5465a <f12afefb7b01f94d6d66d397f323a9914edbf70e
- Affected versionversion=6f6c3c36f0917be24587eeba818ab4fdfcb5465a <f51a540b14eecb8667bbe450192318271b87631e
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo