PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-53292 Linux CVE debrief

CVE-2026-53292 is a vulnerability in the Linux kernel that could lead to a kernel panic. The vulnerability is caused by a BUG_ON() statement in the pn_socket_autobind() function, which is triggered when the pn_socket_bind() function returns -EINVAL and the socket has not been bound. This can happen when the socket's state is not TCP_CLOSE. The vulnerability can be exploited by a user-triggerable path, leading to a denial-of-service (DoS) attack. The issue has been resolved by treating the 'bind returned -EINVAL but pn_port() is still 0' case as a regular error and propagating -EINVAL to the caller instead of crashing.

Vendor
Linux
Product
Unknown
CVSS
MEDIUM 5.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-06-26
Original CVE updated
2026-07-08
Advisory published
2026-06-26
Advisory updated
2026-07-08

Who should care

Linux kernel developers, Linux distribution maintainers, and users of Linux-based systems should be aware of this vulnerability. They should check their systems for the affected kernel versions and apply patches or updates as needed. Additionally, users of Linux-based systems should be cautious when handling untrusted input to prevent exploitation of this vulnerability.

Technical summary

The vulnerability is located in the pn_socket_autobind() function in the net/phonet/socket.c file of the Linux kernel. The function calls pn_socket_bind() with port 0 and checks the return value. If pn_socket_bind() returns -EINVAL, the function assumes the socket was already bound and asserts that the port is non-zero using a BUG_ON() statement. However, pn_socket_bind() also returns -EINVAL when the socket's state is not TCP_CLOSE, even if the socket has never been bound. In this case, the BUG_ON() statement triggers a kernel panic. The fix is to treat this case as a regular error and return -EINVAL to the caller.

Defensive priority

High priority should be given to patching or updating Linux kernel versions affected by this vulnerability. Linux distribution maintainers should update their kernel packages to include the fix. Users of Linux-based systems should apply patches or updates as soon as possible to prevent exploitation.

Recommended defensive actions

  • Apply patches or updates to Linux kernel versions affected by this vulnerability.
  • Check Linux distribution kernel packages for updates and apply them as needed.
  • Monitor Linux-based systems for unusual activity that may indicate exploitation attempts.
  • Consider implementing additional security measures, such as restricting access to sensitive data and services.
  • Perform regular security audits and vulnerability assessments to identify potential vulnerabilities.

Evidence notes

The vulnerability was reported by syzbot and resolved by Linux kernel developers. The fix was backported to stable kernel versions. The CVE record and NVD detail provide additional information about the vulnerability.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-53292 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-53292

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-53292 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-53292

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/5b0c911bcdbd982f7748d11c0b39ec5808eae2de

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/6db58ee730bf434d1afca91b91826e26688856ed

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.