CVE-2021-47086: phonet/pep: refuse to enable an unbound pipe
In the Linux kernel, the following vulnerability has been resolved:
phonet/pep: refuse to enable an unbound pipe
This ioctl() implicitly assumed that the socket was already bound to
a valid local socket name, i.e. Phonet object. If the socket was not
bound, two separate problems would occur:
1) We'd send an pipe enablement request with an invalid source object.
2) Later socket calls could BUG on the socket unexpectedly being
connected yet not bound to a valid object.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel flaw in the Phonet/PEP networking code. An operation could enable a pipe on a socket that had not been properly bound, leaving the kernel in an invalid state and potentially triggering a kernel BUG. Severity is not scored in the provided sources.
Executive priority
Handle through normal kernel patch management unless local exposure to Phonet/PEP is confirmed. There is no sourced evidence of active exploitation, but kernel BUG conditions can affect availability and should not be ignored on exposed or specialized systems.
Technical view
The affected ioctl path assumed a PEP socket already had a valid local Phonet object. If unbound, it could send a pipe enablement request with an invalid source object and later leave the socket connected without a valid bound object, causing unexpected BUG behavior.
Likely exposure
Exposure is limited to systems running affected Linux kernel versions with Phonet/PEP code present and reachable. The source bundle identifies Linux kernel versions around 3.3 through fixed stable lines including 4.4.297, 4.9.295, 4.14.260, 4.19.223, 5.4.169, 5.10.89, 5.15.12, and 5.16, but range details are incomplete.
Exploitation context
The bundle does not cite active exploitation, public weaponization, CVSS, CWE, or KEV listing. Treat exploitation status as unconfirmed. The described impact is kernel correctness and stability from an invalid unbound socket state, not a documented remote compromise path.
Researcher notes
Useful analysis should focus on the ioctl precondition: refusing pipe enablement unless the socket is bound to a valid Phonet object. The provided evidence supports a stability/invariant failure; it does not establish privilege escalation, remote reachability, or exploit maturity.
Mitigation direction
Update Linux kernels to vendor-supported builds containing the referenced stable fixes.
Prioritize systems using or exposing Phonet/PEP functionality.
Check distribution advisories for exact package versions and backported fixes.
Avoid assuming unaffected status from upstream version strings alone.
Validation and detection
Inventory Linux kernel versions across servers, endpoints, appliances, and images.
Confirm whether vendor kernels include the referenced stable commits or equivalent backports.
Review whether Phonet/PEP kernel support is enabled or used in relevant environments.
Track vendor advisory status because the source bundle lacks CVSS and operational mitigations.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2021-47086 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.