Local system crash via missing PCI card data
Published Aug 22, 2024 · Updated May 11, 2026
NULL pointer dereference in the Linux kernel allows local users to crash the system while initializing certain COM20020 PCI devices. In com20020pci_probe(), the driver dereferences the ci pointer even when the matched com20020pci_id_table entry supplies no card information. Reachability requires local access and a matching PCI device with an empty card-information entry; the bounded consequence is a kernel crash.
Summary
What happened
NULL pointer dereference in the Linux kernel allows local users to crash the system while initializing certain COM20020 PCI devices. In com20020pci_probe(), the driver dereferences the ci pointer even when the matched com20020pci_id_table entry supplies no card information. Reachability requires local access and a matching PCI device with an empty card-information entry; the bounded consequence is a kernel crash.
The record
- CVE
- CVE-2022-48908
- Published
- Aug 22, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 22, 2024CVE 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=3.18
- Affected versionversion=8c14f9c70327a6fb75534c4c61d7ea9c82ccf78f <5f394102ee27dbf051a4e283390cd8d1759dacea
- Affected versionversion=8c14f9c70327a6fb75534c4c61d7ea9c82ccf78f <8e3bc7c5bbf87e86e9cd652ca2a9166942d86206
- Affected versionversion=8c14f9c70327a6fb75534c4c61d7ea9c82ccf78f <b1ee6b9340a38bdb9e5c90f0eac5b22b122c3049
- Affected versionversion=8c14f9c70327a6fb75534c4c61d7ea9c82ccf78f <b838add93e1dd98210482dc433768daaf752bdef
- Affected versionversion=8c14f9c70327a6fb75534c4c61d7ea9c82ccf78f <bd6f1fd5d33dfe5d1b4f2502d3694a7cc13f166d
- Affected versionversion=8c14f9c70327a6fb75534c4c61d7ea9c82ccf78f <ca0bdff4249a644f2ca7a49d410d95b8dacf1f72
- Affected versionversion=8c14f9c70327a6fb75534c4c61d7ea9c82ccf78f <e50c589678e50f8d574612e473ca60ef45190896
- Affected versionversion=8c14f9c70327a6fb75534c4c61d7ea9c82ccf78f <ea372aab54903310756217d81610901a8e66cb7d
What conditions does exploitation require?
What is affected?
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
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