Kernel memory corruption via unchecked NFC lengths
Published Oct 21, 2024 · Updated Aug 5, 2026
Out-of-bounds write in the Linux kernel NFC NCI stack allows local users to corrupt kernel memory through malformed target data. nci_add_new_protocol copies attacker-controlled NFC-A identifiers and NFC-B or NFC-F response data into fixed-size nfc_target arrays without checking their declared lengths. Low-privileged local access and an enabled NCI NFC path are required; triggering the defect can damage kernel state or interrupt the system.
Summary
What happened
Out-of-bounds write in the Linux kernel NFC NCI stack allows local users to corrupt kernel memory through malformed target data. nci_add_new_protocol copies attacker-controlled NFC-A identifiers and NFC-B or NFC-F response data into fixed-size nfc_target arrays without checking their declared lengths. Low-privileged local access and an enabled NCI NFC path are required; triggering the defect can damage kernel state or interrupt the system.
The record
- CVE
- CVE-2022-48967
- Published
- Oct 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-129
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 <27eb2d7a1b9987b6d0429b7716b1ff3b82c4ffc9
- Affected versionversion=019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 <6778434706940b8fad7ef35f410d2b9929f256d2
- Affected versionversion=019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 <6b37f0dc0638d13a006f2f24d2f6ca61e83bc714
- Affected versionversion=019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 <908b2da426fe9c3ce74cf541ba40e7a4251db191
- Affected versionversion=019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 <cff35329070b96b4484d23f9f48a5ca2c947e750
- Affected versionversion=019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 <dbdcfb9f6748218a149f62468d6297ce3f014e9c
- Affected versionversion=019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 <e329e71013c9b5a4535b099208493c7826ee4a64
- Affected versionversion=019c4fbaa790e2b3f11dab0c8b7d9896d77db3e5 <f41547546db9af99da2c34e3368664d7a79cefae
- Affected versionversion=3.4
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
Public exploit references
- syzbot nci_add_new_protocol reproducerproof of concept · demonstrated
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