LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46205: staging: media: atomisp: Disallow all private IOCTLs

In the Linux kernel, the following vulnerability has been resolved: staging: media: atomisp: Disallow all private IOCTLs Disallow all private IOCTLs. These aren't quite as safe as one could assume of IOCTL handlers; disable them for now. Instead of removing the code, return in the beginning of the function if cmd is non-zero in order to keep static checkers happy.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw concerns unsafe private control requests in the staging AtomISP media driver. An attacker already possessing low-privileged local access could potentially cause severe confidentiality, integrity, and availability impacts. Systems that do not include or use AtomISP are less likely to be exposed, but the supplied records do not fully define runtime prerequisites.

Executive priority

Treat as a high-priority local privilege-boundary issue, especially on shared, kiosk, development, or otherwise untrusted-user systems using AtomISP hardware. It is less urgent than remotely exploitable or confirmed-active threats. Require rapid exposure identification and normal emergency kernel patching where the driver is present; avoid assuming every Linux server is affected.

Technical view

AtomISP accepted private IOCTL commands that kernel maintainers considered insufficiently safe. The resolution rejects every non-zero private command at the beginning of the handler. The assigned CVSS 3.1 score is 7.8: local access, low complexity, low privileges, no user interaction, and high impacts. No CWE or detailed underlying memory-safety mechanism is provided.

Likely exposure

Exposure is limited to affected Linux kernels where the staging AtomISP media driver is present and reachable by a low-privileged local user. The source lists affected version entries from 4.12 through 7.1, but provides no distribution-package mapping. Internet exposure alone is not sufficient because the CVSS vector specifies local access.

Exploitation context

The supplied sources do not report active exploitation, and the CVE is not marked as CISA KEV. Exploitation requires existing low-privileged local access according to the CVSS vector. Public details establish that private IOCTL handling was disabled, but do not describe a demonstrated exploit, vulnerable operation, or precise failure mode.

Researcher notes

The public description is unusually sparse: it identifies unsafe private IOCTL handling but no specific corruption primitive, CWE, affected command, or proof of exploitation. The duplicated and unconventional version entries make downstream applicability uncertain. Researchers should use vendor backport data and the referenced stable commits to establish exact package status without inferring exploitability from CVSS alone.

Mitigation direction

  • Install the applicable vendor-supported kernel update containing the referenced AtomISP fix.
  • Match distribution kernel packages against vendor advisories rather than relying only on upstream version numbers.
  • Prioritize multi-user systems where untrusted users can access AtomISP media devices.
  • If updates are unavailable, obtain interim exposure-reduction guidance from the Linux distribution vendor.

Validation and detection

  • Inventory kernel versions and map them to distribution security advisories for CVE-2026-46205.
  • Determine whether the AtomISP staging driver is built, loaded, or used on each system.
  • Confirm the updated kernel incorporates the applicable referenced stable commit.
  • Verify private non-zero AtomISP IOCTL requests are rejected after remediation.
  • Recheck affected systems after rebooting into the updated kernel.
Prepared
Confidence
medium
Sources
11

Public sources used

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-2026-46205 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
3Timeline events
0ADP providers
10Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-46205Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa49d25364dfb9f8a64037488a39ab1f56c5fa419, ad85094b293e40e7a2f831b0311a389d952ebd5e, ad85094b293e40e7a2f831b0311a389d952ebd5e, ad85094b293e40e7a2f831b0311a389d952ebd5e, ad85094b293e40e7a2f831b0311a389d952ebd5e, ad85094b293e40e7a2f831b0311a389d952ebd5e, ad85094b293e40e7a2f831b0311a389d952ebd5e, ad85094b293e40e7a2f831b0311a389d952ebd5e, ad85094b293e40e7a2f831b0311a389d952ebd5eunaffected
LinuxLinux4.12, 5.8, 0, 4.18, 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.90, 6.18.32, 7.0.9, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.