LiveActive security incident?Get immediate response
CVE Record

CVE-2024-39464: media: v4l: async: Fix notifier list entry init

In the Linux kernel, the following vulnerability has been resolved: media: v4l: async: Fix notifier list entry init struct v4l2_async_notifier has several list_head members, but only waiting_list and done_list are initialized. notifier_entry was kept 'zeroed' leading to an uninitialized list_head. This results in a NULL-pointer dereference if csi2_async_register() fails, e.g. node for remote endpoint is disabled, and returns -ENOTCONN. The following calls to v4l2_async_nf_unregister() results in a NULL pointer dereference. Add the missing list head initializer.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-39464 is a Linux kernel bug in the media/video async notifier code. Under a specific failure path, the kernel can dereference a null pointer, which can crash affected systems. The sources do not provide CVSS, remote attack evidence, or active exploitation evidence.

Executive priority

Treat as a targeted stability risk for Linux platforms with media hardware, not a confirmed internet-scale emergency. Patch through normal kernel maintenance, with higher priority for appliances, embedded fleets, and systems where a kernel crash affects safety or availability.

Technical view

The bug is a missing initializer for the v4l2_async_notifier notifier_entry list_head. If csi2_async_register() fails, for example with -ENOTCONN when a remote endpoint node is disabled, v4l2_async_nf_unregister() can later hit a NULL pointer dereference. Kernel stable commits add the missing list head initializer.

Likely exposure

Exposure is most likely on Linux systems using affected 6.6, 6.9, or 6.10 kernel lines with V4L/media async notifier paths, especially camera or CSI2-related configurations. General servers without relevant media hardware or drivers are less likely exposed, but kernel packaging must be checked.

Exploitation context

The provided bundle says this CVE is not in KEV and includes no cited evidence of active exploitation. The described impact is a kernel NULL-pointer dereference on a driver failure path, which points primarily to denial of service rather than data compromise.

Researcher notes

Evidence is limited to the kernel CVE description and stable commit references. No CVSS, CWE, exploitability analysis, or public exploitation signal is included. Validation should focus on affected kernel lineage, presence of media async notifier code paths, and vendor backport confirmation.

Mitigation direction

  • Apply Linux kernel or vendor firmware updates containing the referenced stable fixes.
  • Check distribution or device-vendor advisories for backported fixed kernel packages.
  • Prioritize embedded, camera, and CSI2-capable systems running affected kernel lines.
  • Avoid deploying affected custom kernels when relevant media drivers are enabled.

Validation and detection

  • Inventory kernel versions across Linux hosts and embedded devices.
  • Identify systems using V4L/media, camera, or CSI2-related drivers.
  • Confirm vendor kernel packages include one of the referenced stable commits or equivalent backport.
  • Review kernel logs for media async registration failures or related NULL-pointer dereferences.
Prepared
Confidence
medium
Sources
5

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-2024-39464 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
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb8ec754ae4c563f6aab8c0cb47aeb2eae67f1da3, b8ec754ae4c563f6aab8c0cb47aeb2eae67f1da3, b8ec754ae4c563f6aab8c0cb47aeb2eae67f1da3unaffected
LinuxLinux6.6, 0, 6.6.34, 6.9.5, 6.10affected
Weakness

CWE details

No CWE listed

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