PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-90392 Linux CVE debrief

A potential use-after-free (UAF) vulnerability was found in the Linux kernel when reading BPF link information. The issue arises from accessing the link->prog pointer without holding any locks, which can lead to a UAF issue if the prog is concurrently replaced via bpf_link_update. This vulnerability has been resolved by accessing link->prog under RCU protection.

Vendor
Linux
Product
Unknown
CVSS
HIGH 7.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-17
Original CVE updated
2026-09-18
Advisory published
2026-09-17
Advisory updated
2026-09-18

Who should care

Linux kernel administrators, security teams, and developers using BPF links should assess exposure and prioritize verification of affected systems, especially those with BPF link usage. Linux kernel users should verify BPF link usage, assess exposure, and prioritize verification of affected systems.

Why it matters

CVE-2026-90392 is a potential use-after-free vulnerability in the Linux kernel when reading BPF link information. Linux kernel users should assess exposure, prioritize verification of affected systems, and apply patches or updates to mitigate the vulnerability.

  • Verification of BPF link usage and system configurations is necessary to determine exposure.
  • Potential UAF issues can lead to system instability or crashes if exploited.
  • Applying patches or updates provided by the Linux kernel maintainers can mitigate the vulnerability.

Technical summary

The Linux kernel vulnerability (CVE-2026-90392) involves a potential use-after-free issue when reading BPF link information. The problem occurs because link->prog is accessed without locks, allowing for concurrent replacement via bpf_link_update, which can lead to a UAF issue. The fix involves accessing link->prog under RCU protection. Linux kernel users should assess exposure and prioritize verification of affected systems, especially those with BPF link usage. This vulnerability has been resolved by accessing link->prog under RCU protection to safely fetch the pointer and guarantee its lifetime while reading its fields.

Defensive priority

Linux kernel users should assess exposure and prioritize verification of affected systems, especially those with BPF link usage.

Recommended defensive actions

  • Assess exposure of Linux kernel systems using BPF links
  • Verify system configurations and BPF link usage
  • Apply patches or updates provided by the Linux kernel maintainers
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but specific affected versions and exploitation details are not provided. Linux kernel users should verify BPF link usage, assess exposure, and prioritize verification of affected systems. Defensive verification tasks include reviewing system configurations, BPF link usage, and applying patches or updates provided by the Linux kernel maintainers.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-90392 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-90392 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

    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/79347e42cfbc9e78872922e8f08a70609c9af82f

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

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/85cf991c881e7198be32be05a9daa2625390c8b3

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

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/863f3ddd0b8ac65abfb50d3be0869268ac0e277b

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

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/a5c936ac904767fc1d943d40b0308bcb2ae2509b

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

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/d7d7208e2603b45724b684f4df73904fb347741e

    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.