Security readout for executives and security teams
Plain-English summary
A race in Linux network-device cleanup can access a device after its memory has been freed. A successful local attack could compromise confidentiality, integrity, and availability. The flaw is serious, but the supplied evidence does not establish remote reachability or real-world exploitation.
Executive priority
Treat as a high-priority kernel update, especially on shared or locally accessible Linux systems. It is not supported as an internet-wide emergency because exploitation is local and no active exploitation is documented. Resolve version ambiguity through vendor advisories before setting compliance deadlines.
Technical view
The linkwatch queue released a network-device reference before completing all device accesses. Concurrent cleanup could then free the device, causing netdev_unlock_ops() to read freed memory. The kernel fix moves __dev_put() into callers so the reference is released only after access finishes.
Likely exposure
Exposure is limited to affected Linux kernels and requires local access with sufficient ability to manipulate network-device state. The bundle lists 6.15, 6.18.10, 6.19, and an ambiguous “0” as affected; administrators should verify exact ranges with their distribution.
Exploitation context
The CVSS vector is local, low-complexity, low-privilege, and requires no user interaction. A KASAN-confirmed reproducer exists in the disclosure. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public weaponized exploit.
Researcher notes
The documented failure is a reference-lifetime race between linkwatch processing and net-device teardown. The source describes moving __dev_put() after all accesses rather than adding conditional ops locking. Exact affected and fixed release ranges are incomplete or ambiguous in the supplied bundle, so commit ancestry and vendor backports require confirmation.
Mitigation direction
- Apply a vendor kernel update containing the published linkwatch fix.
- Confirm fixed packages with the Linux distribution or appliance vendor.
- Prioritize multi-user systems where untrusted users can manipulate network devices.
- Restrict unnecessary local access and network-device administration until patched.
Validation and detection
- Inventory running kernel versions across Linux hosts and appliances.
- Compare vendor package advisories against both referenced stable-kernel commits.
- Verify the patched kernel is running after installation and reboot.
- Use safe staging tests or sanitizers to check for regression symptoms.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2026-23192 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/2718ae6af7445ba2ee0abf6365ca43a9a3b16aebCVE reference, Linux
- https://git.kernel.org/stable/c/83b67cc9be9223183caf91826d9c194d7fb128faCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.