Sensitive information disclosure via failed Phonet accepts
Published Dec 16, 2021 · Updated Aug 4, 2024
Reference-count leakage in the Linux kernel 5.15.8 and earlier allows local users to read sensitive data via failed Phonet socket accepts. In net/phonet/pep.c, pep_sock_accept() acquires a reference with sock_hold() but fails to release it when pep_accept_conn() returns an error. Exploitation requires local low-privileged access and a kernel built with Phonet support; the bounded reported impact is sensitive-information disclosure, not modification or service interruption.
Summary
What happened
Reference-count leakage in the Linux kernel 5.15.8 and earlier allows local users to read sensitive data via failed Phonet socket accepts. In net/phonet/pep.c, pep_sock_accept() acquires a reference with sock_hold() but fails to release it when pep_accept_conn() returns an error. Exploitation requires local low-privileged access and a kernel built with Phonet support; the bounded reported impact is sensitive-information disclosure, not modification or service interruption.
The record
- CVE
- CVE-2021-45095
- Published
- Dec 16, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-200
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 16, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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