Kernel misbehavior via torn sk_prot reads
Published Oct 17, 2022 · Updated Apr 15, 2025
A data race in the Linux kernel IPv6 implementation allows remote authenticated users on an adjacent network to trigger undesired behavior. Functions in inet6_stream_ops and inet6_dgram_ops read sk->sk_prot without socket or RTNL locking and without READ_ONCE, allowing load tearing while IPV6_ADDRFORM changes the pointer. Exploitation requires adjacent-network access, low privileges, and high complexity; public sources do not define the resulting behavior more precisely.
Summary
What happened
A data race in the Linux kernel IPv6 implementation allows remote authenticated users on an adjacent network to trigger undesired behavior. Functions in inet6_stream_ops and inet6_dgram_ops read sk->sk_prot without socket or RTNL locking and without READ_ONCE, allowing load tearing while IPV6_ADDRFORM changes the pointer. Exploitation requires adjacent-network access, low privileges, and high complexity; public sources do not define the resulting behavior more precisely.
The record
- CVE
- CVE-2022-3567
- Published
- Oct 17, 2022
- Updated
- Apr 15, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-362
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 17, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 2025Record 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=n/a
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