Kernel memory disclosure or crash via stale notifier
Published Jan 11, 2025 · Updated May 11, 2026
Invalid memory access in the Linux kernel igb driver allows local users to disclose kernel memory or crash the system after registration fails. igb_init_module registers the DCA notifier before pci_register_driver and fails to unregister it when PCI driver registration returns an error, leaving a callback able to access invalid state. Exploitation requires local low-privileged access, failed igb driver installation, and subsequent invocation of the lingering notifier.
Summary
What happened
Invalid memory access in the Linux kernel igb driver allows local users to disclose kernel memory or crash the system after registration fails. igb_init_module registers the DCA notifier before pci_register_driver and fails to unregister it when PCI driver registration returns an error, leaving a callback able to access invalid state. Exploitation requires local low-privileged access, failed igb driver installation, and subsequent invocation of the lingering notifier.
The record
- CVE
- CVE-2024-52332
- Published
- Jan 11, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 11, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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=2.6.29
- Affected versionversion=bbd98fe48a43464b4a044bc4cbeefad284d6aa80 <0566f83d206c7a864abcd741fe39d6e0ae5eef29
- Affected versionversion=bbd98fe48a43464b4a044bc4cbeefad284d6aa80 <4458046617dfadc351162dbaea1945c57eebdf36
- Affected versionversion=bbd98fe48a43464b4a044bc4cbeefad284d6aa80 <4fe517643f529e805bb6b890a4331c100e8f2484
- Affected versionversion=bbd98fe48a43464b4a044bc4cbeefad284d6aa80 <8009cdcc493fa30d4572016daf2d6999da4d6c54
- Affected versionversion=bbd98fe48a43464b4a044bc4cbeefad284d6aa80 <992fd34122de377b45cb75b64fc7f17fc1e6ed2f
- Affected versionversion=bbd98fe48a43464b4a044bc4cbeefad284d6aa80 <e0155b1b1509d0ef4799bd1cd73309ca466df3f3
- Affected versionversion=bbd98fe48a43464b4a044bc4cbeefad284d6aa80 <f309733a8c9da7d4266a8a3755020b738a570cae
What conditions does exploitation require?
What is affected?
Published CVSS scores
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