Security readout for executives and security teams
Plain-English summary
A Linux kernel media-driver regression can access an internal buffer after it has been freed. A local, low-privileged attacker may be able to crash the system or compromise confidentiality and integrity. Exposure depends on running an affected kernel and using the iris media driver; the supplied sources do not establish broader reachability.
Executive priority
Treat this as a high-priority kernel update for systems using the iris media driver, especially shared or locally accessible machines. It is not presented as remotely exploitable, and active exploitation is unconfirmed. Use normal emergency-change evaluation rather than assuming universal exposure; accelerate remediation where an affected kernel and relevant hardware or workload coincide.
Technical view
Commit 1dabf00ee206 introduced a use-after-free in iris_release_internal_buffers(): session_release_buf() may free buffer, but its caller subsequently accesses it. The fix marks the buffer pending release before that call and restores the flag if release fails, preventing a post-free dereference. No CWE is assigned in the supplied record.
Likely exposure
The supplied record marks Linux versions 7.0, 6.18.32, 7.0.9, and 7.1 as affected, while listing several commits and versions as unaffected. Practical exposure requires the relevant iris media-driver path. Distribution backports may make version-only checks unreliable, so confirm patch ancestry or vendor status.
Exploitation context
CVSS 3.1 is 7.8: local access, low complexity, low privileges, no user interaction, and potentially high confidentiality, integrity, and availability impact. The record is not in KEV, and the supplied sources provide no evidence of active exploitation or a public exploit.
Researcher notes
The vulnerable lifetime transition occurs because session_release_buf() can free buffer before iris_release_internal_buffers() finishes using it. The corrective ordering sets BUF_ATTR_PENDING_RELEASE first and rolls it back on failure. The supplied version data is unusual and incomplete for distribution kernels; validate using commit ancestry and vendor backport records. No exploitability proof or affected configuration matrix is supplied.
Mitigation direction
- Install a vendor-supported kernel containing the applicable upstream or stable fix.
- Check distribution advisories because vendors may backport fixes without changing the expected upstream version.
- Prioritize systems where the iris media driver is present and used.
- If patching is delayed, consult vendor guidance for supported exposure-reduction measures.
Validation and detection
- Inventory running kernel builds and compare them with vendor advisories and the CVE record.
- Determine whether the iris media driver is present and operational on each system.
- Confirm the deployed kernel contains the applicable stable fix commit or documented backport.
- After updating, verify systems boot normally and affected media workloads complete without regressions.
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-46240 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/dd24998a4a4016fb9921916024399bd80f0d45c6CVE reference, Linux
- https://git.kernel.org/stable/c/18c64439f249859b6140f7bf8bcf95c8ed841f28CVE reference, Linux
- https://git.kernel.org/stable/c/f27cfdcfc916bb59297825805f4c3499f89f9e76CVE 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.