Kernel-memory disclosure via uninitialized TIPC socket address
Published Feb 11, 2022 · Updated Aug 2, 2024
Information disclosure in Linux Kernel before 5.17-rc1 allows local users to read kernel memory through a crafted TIPC datagram. The __tipc_sendmsg() path leaves a four-byte hole in tipc_socket_addr.ref uninitialized, and __tipc_getname() copies that address to user space. A low-privilege local account with access to TIPC sockets is required, and each operation exposes no more than seven attacker-uncontrolled bytes.
Summary
What happened
Information disclosure in Linux Kernel before 5.17-rc1 allows local users to read kernel memory through a crafted TIPC datagram. The __tipc_sendmsg() path leaves a four-byte hole in tipc_socket_addr.ref uninitialized, and __tipc_getname() copies that address to user space. A low-privilege local account with access to TIPC sockets is required, and each operation exposes no more than seven attacker-uncontrolled bytes.
The record
- CVE
- CVE-2022-0382
- Published
- Feb 11, 2022
- Updated
- Aug 2, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 11, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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=Linux kernel versions prior to 5.17-rc1
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
No sourced classifications are available.
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