LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46222: media: rockchip: rkcif: Add missing MUST_CONNECT flag to pads

In the Linux kernel, the following vulnerability has been resolved: media: rockchip: rkcif: Add missing MUST_CONNECT flag to pads The pads missed checks for connected devices which may a null dereference when the stream is enabled. Unable to handle kernel NULL pointer dereference at virtual address 0000000000000020 pc : rkcif_interface_enable_streams+0x48/0xf0 lr : rkcif_interface_enable_streams+0x44/0xf0 Call trace: rkcif_interface_enable_streams+0x48/0xf0 v4l2_subdev_enable_streams+0x26c/0x3f0 rkcif_stream_start_streaming+0x140/0x278 vb2_start_streaming+0x74/0x188 vb2_core_streamon+0xe0/0x1d8 vb2_ioctl_streamon+0x60/0xa8 v4l_streamon+0x2c/0x40 __video_do_ioctl+0x34c/0x400 video_usercopy+0x2d0/0x800 video_ioctl2+0x20/0x60 v4l2_ioctl+0x48/0x78

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel flaw in the Rockchip camera interface driver. If streaming is enabled when expected connected media pads are absent, the kernel can hit a null pointer dereference. The practical business risk is likely device instability or denial of service on affected Rockchip-based systems, not broad internet exposure.

Executive priority

Treat this as a targeted platform stability issue. Prioritize embedded, appliance, or edge deployments using Rockchip camera hardware. It is not currently supported as an emergency internet-wide exploitation risk by the supplied sources.

Technical view

The rkcif media driver lacked MUST_CONNECT validation on pads. The CVE record shows a null dereference in rkcif_interface_enable_streams during V4L2 stream enablement, reached through video ioctl stream-on paths. The published fix adds the missing pad connection requirement in Linux stable commits.

Likely exposure

Exposure appears limited to Linux systems using affected kernel versions with the Rockchip rkcif media driver and relevant camera pipeline configuration. General Linux servers without this hardware or driver are unlikely to be exposed based on the provided sources.

Exploitation context

No provided source reports active exploitation, public exploit code, or CISA KEV listing. The call trace implies the crash occurs when a V4L2 stream is enabled, so local device access may matter. Evidence is insufficient to assess privilege requirements fully.

Researcher notes

The source bundle does not include CVSS, CWE, exploit status, or detailed affected-version ranges beyond the CVE metadata. Analysis should focus on rkcif pad topology validation, V4L2 stream-on paths, and whether downstream kernels carry either stable fix.

Mitigation direction

  • Update to a Linux kernel containing the referenced stable fixes.
  • Check distribution or device vendor advisories for backported kernel packages.
  • Restrict access to video device nodes to trusted users and services until patched.
  • Disable the Rockchip rkcif camera interface if it is not operationally required.

Validation and detection

  • Inventory affected systems for Rockchip-based Linux devices using the rkcif media driver.
  • Confirm whether deployed kernels include the referenced stable commits or vendor backports.
  • Review kernel logs for null dereferences in rkcif_interface_enable_streams.
  • Verify camera streaming workflows after patching to confirm stability.
Prepared
Confidence
medium
Sources
4

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-46222 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux85411d17bee99b0a99e983f37188f9cdacfded54, 85411d17bee99b0a99e983f37188f9cdacfded54unaffected
LinuxLinux6.19, 0, 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.