Local kernel crash via unbound pipe enablement
Published Mar 4, 2024 · Updated May 11, 2026
Improper state validation in the Linux kernel allows local users to trigger a kernel BUG through an unbound Phonet PEP socket. The ioctl path in net/phonet/pep.c sends a pipe-enable request with an invalid source object and leaves the unbound socket connected. A local low-privileged user must open an unbound Phonet PEP socket and invoke pipe enablement; subsequent socket operations can crash the kernel.
Summary
What happened
Improper state validation in the Linux kernel allows local users to trigger a kernel BUG through an unbound Phonet PEP socket. The ioctl path in net/phonet/pep.c sends a pipe-enable request with an invalid source object and leaves the unbound socket connected. A local low-privileged user must open an unbound Phonet PEP socket and invoke pipe enablement; subsequent socket operations can crash the kernel.
The record
- CVE
- CVE-2021-47086
- Published
- Mar 4, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 4, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=3.3
- Affected versionversion=bdb6e697b2a76c541960b86ab8fda88f3de1adf2 <0bbdd62ce9d44f3a22059b3d20a0df977d9f6d59
- Affected versionversion=bdb6e697b2a76c541960b86ab8fda88f3de1adf2 <311601f114859d586d5ef8833d60d3aa23282161
- Affected versionversion=bdb6e697b2a76c541960b86ab8fda88f3de1adf2 <48c76fc53582e7f13c1e0b11c916e503256c4d0b
- Affected versionversion=bdb6e697b2a76c541960b86ab8fda88f3de1adf2 <52ad5da8e316fa11e3a50b3f089aa63e4089bf52
- Affected versionversion=bdb6e697b2a76c541960b86ab8fda88f3de1adf2 <53ccdc73eedaf0e922c45b569b797d2796fbaafa
- Affected versionversion=bdb6e697b2a76c541960b86ab8fda88f3de1adf2 <75a2f31520095600f650597c0ac41f48b5ba0068
- Affected versionversion=bdb6e697b2a76c541960b86ab8fda88f3de1adf2 <982b6ba1ce626ef87e5c29f26f2401897554f235
- Affected versionversion=bdb6e697b2a76c541960b86ab8fda88f3de1adf2 <b10c7d745615a092a50c2e03ce70446d2bec2aca
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