Local privilege escalation via nf_queue socket use-after-free
Published Aug 22, 2024 · Updated Aug 5, 2026
A use-after-free in Linux kernel nf_queue 2.6.29 through 5.16.12 allows local users to disclose or corrupt kernel memory via an NFQUEUE race. __nf_queue calls sock_hold() on state->sk without ensuring that the socket reference count remains nonzero, allowing a dying socket to be reused after release. Exploitation requires CAP_NET_ADMIN obtainable in an unprivileged user and network namespace, and successful abuse allows arbitrary kernel memory read or write, control-flow hijacking, or a kernel panic without victim interaction.
Summary
What happened
A use-after-free in Linux kernel nf_queue 2.6.29 through 5.16.12 allows local users to disclose or corrupt kernel memory via an NFQUEUE race. __nf_queue calls sock_hold() on state->sk without ensuring that the socket reference count remains nonzero, allowing a dying socket to be reused after release. Exploitation requires CAP_NET_ADMIN obtainable in an unprivileged user and network namespace, and successful abuse allows arbitrary kernel memory read or write, control-flow hijacking, or a kernel panic without victim interaction.
The record
- CVE
- CVE-2022-48911
- Published
- Aug 22, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 22, 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=2.6.29
- Affected versionversion=271b72c7fa82c2c7a795bc16896149933110672d <21b27b2baa27423286e9b8d3f0b194d587083d95
- Affected versionversion=271b72c7fa82c2c7a795bc16896149933110672d <34dc4a6a7f261736ef7183868a5bddad31c7f9e3
- Affected versionversion=271b72c7fa82c2c7a795bc16896149933110672d <43c25da41e3091b31a906651a43e80a2719aa1ff
- Affected versionversion=271b72c7fa82c2c7a795bc16896149933110672d <4d05239203fa38ea8a6f31e228460da4cb17a71a
- Affected versionversion=271b72c7fa82c2c7a795bc16896149933110672d <c3873070247d9e3c7a6b0cf9bf9b45e8018427b1
- Affected versionversion=271b72c7fa82c2c7a795bc16896149933110672d <dcc3cb920bf7ba66ac5e9272293a9ba5f80917ee
- Affected versionversion=271b72c7fa82c2c7a795bc16896149933110672d <dd648bd1b33a828f62befa696b206c688da0ec43
- Affected versionversion=271b72c7fa82c2c7a795bc16896149933110672d <ef97921ccdc243170fcef857ba2a17cf697aece5
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.
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