Kernel memory corruption via stale AF_UNIX peer pointer
Published Jun 24, 2026 · Updated Jun 24, 2026
Use-after-free in the Linux kernel's AF_UNIX sockmap iterator allows local users to corrupt kernel memory through a controlled socket-close race. unix_stream_bpf_update_proto() reads the peer pointer without the socket state lock, so unix_release_sock() can clear and free it before sock_hold() increments its reference count. Exploitation requires local low-privilege access with delegated BPF capabilities and a successful AF_UNIX close race; the bounded result is kernel memory corruption.
Summary
What happened
Use-after-free in the Linux kernel's AF_UNIX sockmap iterator allows local users to corrupt kernel memory through a controlled socket-close race. unix_stream_bpf_update_proto() reads the peer pointer without the socket state lock, so unix_release_sock() can clear and free it before sock_hold() increments its reference count. Exploitation requires local low-privilege access with delegated BPF capabilities and a successful AF_UNIX close race; the bounded result is kernel memory corruption.
The record
- CVE
- CVE-2026-53033
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-825, CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 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=2c860a43dd77f969bb959336a2f743d7103a8f63 <1a59cc6b65fd3ad9915aae5970d859109d4ce9fb
- Affected versionversion=2c860a43dd77f969bb959336a2f743d7103a8f63 <64c2f93fc3254d3bf5de4445fb732ee5c451edb6
- Affected versionversion=2c860a43dd77f969bb959336a2f743d7103a8f63 <921920c34cb591947dd30c692500795a69f1e3fa
- Affected versionversion=2c860a43dd77f969bb959336a2f743d7103a8f63 <98f744d204e5d6fca589cd2c44c3190a0c71697f
- Affected versionversion=2c860a43dd77f969bb959336a2f743d7103a8f63 <c6f4015eac2e3cbc3cb7a17539e10bbb5c2049c3
- Affected versionversion=2c860a43dd77f969bb959336a2f743d7103a8f63 <d0d124dbcef9318e326956137b31671407094bd4
- Affected versionversion=5.15
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
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