LiveActive security incident?Get immediate response
CVE Record

CVE-2024-58004: media: intel/ipu6: remove cpu latency qos request on error

In the Linux kernel, the following vulnerability has been resolved: media: intel/ipu6: remove cpu latency qos request on error Fix cpu latency qos list corruption like below. It happens when we do not remove cpu latency request on error path and free corresponding memory. [ 30.634378] l7 kernel: list_add corruption. prev->next should be next (ffffffff9645e960), but was 0000000100100001. (prev=ffff8e9e877e20a8). [ 30.634388] l7 kernel: WARNING: CPU: 2 PID: 2008 at lib/list_debug.c:32 __list_add_valid_or_report+0x83/0xa0 <snip> [ 30.634640] l7 kernel: Call Trace: [ 30.634650] l7 kernel: <TASK> [ 30.634659] l7 kernel: ? __list_add_valid_or_report+0x83/0xa0 [ 30.634669] l7 kernel: ? __warn.cold+0x93/0xf6 [ 30.634678] l7 kernel: ? __list_add_valid_or_report+0x83/0xa0 [ 30.634690] l7 kernel: ? report_bug+0xff/0x140 [ 30.634702] l7 kernel: ? handle_bug+0x58/0x90 [ 30.634712] l7 kernel: ? exc_invalid_op+0x17/0x70 [ 30.634723] l7 kernel: ? asm_exc_invalid_op+0x1a/0x20 [ 30.634733] l7 kernel: ? __list_add_valid_or_report+0x83/0xa0 [ 30.634742] l7 kernel: plist_add+0xdd/0x140 [ 30.634754] l7 kernel: pm_qos_update_target+0xa0/0x1f0 [ 30.634764] l7 kernel: cpu_latency_qos_update_request+0x61/0xc0 [ 30.634773] l7 kernel: intel_dp_aux_xfer+0x4c7/0x6e0 [i915 1f824655ed04687c2b0d23dbce759fa785f6d033]

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can corrupt an internal CPU latency QoS list when an Intel IPU6 media driver error path frees memory without removing its request. The public record shows a kernel warning and list corruption, but does not provide CVSS, confirmed impact, or active exploitation evidence.

Executive priority

Handle through normal kernel patch management unless your environment broadly uses affected Linux kernels with Intel IPU6 hardware paths. There is no provided evidence of active exploitation, but kernel memory/list corruption can affect system reliability and should not be ignored.

Technical view

The flaw is in the Linux kernel media intel/ipu6 path. On an error path, a cpu latency QoS request is not removed before its memory is freed, causing list corruption later seen through pm_qos and cpu_latency_qos_update_request call paths. Stable kernel commits are referenced as the resolution.

Likely exposure

Exposure appears limited to Linux systems running affected kernel builds that include and exercise the Intel IPU6 media driver path. The provided affected data names Linux and lists kernel versions/build identifiers, but does not identify distributions, devices, or configurations.

Exploitation context

The source bundle does not show CISA KEV listing, public exploitation, exploit availability, or a described attacker path. Treat this as a stability and kernel-memory-safety issue until vendor advisories provide clearer exploitability and impact information.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit preconditions, privilege requirements, or confirmed security impact are provided. The strongest technical signal is the upstream fix for a freed QoS request left on an internal list, producing list_add corruption in kernel diagnostics.

Mitigation direction

  • Update to a kernel package containing the referenced stable fixes.
  • Check distribution or vendor advisories for backported CVE-2024-58004 fixes.
  • Prioritize systems with Intel IPU6 media support enabled or present.
  • Track kernel update status through normal patch management.
  • Avoid custom mitigation claims unless confirmed by kernel or distribution guidance.

Validation and detection

  • Inventory Linux systems and kernel versions against vendor fixed-package guidance.
  • Confirm whether Intel IPU6 media driver support is present in relevant builds.
  • Check kernel source or package changelogs for the referenced stable commits.
  • Review logs for list corruption warnings matching the described QoS path.
  • Document systems awaiting vendor-fixed kernel packages.
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-58004 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
4Source 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf50c4ca0a82003b8a542c3332fd292cf1bc355a2, f50c4ca0a82003b8a542c3332fd292cf1bc355a2, f50c4ca0a82003b8a542c3332fd292cf1bc355a2unaffected
LinuxLinux6.10, 0, 6.12.14, 6.13.3, 6.14affected
Weakness

CWE details

No CWE listed

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