Review reviewHigh

CVE-2024-44949

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: parisc: fix a possible DMA corruption ARCH_DMA_MINALIGN was defined as 16 - this is too small - it may be possible that two unrelated 16-byte allocations share a cache line. If one of these allocations is written using DMA and the other is written using cached write, the value that was written with DMA may be corrupted. This commit changes ARCH_DMA_MINALIGN to be 128 on PA20 and 32 on PA1.1 - that's the largest possible cache line size. As different parisc microarchitectures have different cache line size, we define arch_sl...

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2024.09.05
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: parisc: fix a possible DMA corruption ARCH_DMA_MINALIGN was defined as 16 - this is too small - it may be possible that two unrelated 16-byte allocations share a cache line. If one of these allocations is written using DMA and the other is written using cached write, the value that was written with DMA may be corrupted. This commit changes ARCH_DMA_MINALIGN to be 128 on PA20 and 32 on PA1.1 - that's the largest possible cache line size. As different parisc microarchitectures have different cache line size, we define arch_sl...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= a01fece2e4185ac173abd16d10304d73d47ebf00 < 00baca74fb5879e5f9034b6156671301f500f8ee, >= a01fece2e4185ac173abd16d10304d73d47ebf00 < 642a0b7453daff0295310774016fcb56d1f5bc7f, >= a01fece2e4185ac173abd16d10304d73d47ebf00 < 533de2f470baac40d3bf622fe631f15231a03c9f, >= a01fece2e4185ac173abd16d10304d73d47ebf00 < 7ae04ba36b381bffe2471eff3a93edced843240f, >= 4.4, < 6.6.46, >= 6.7 < 6.10.5, 6.11
Fixed versions
6.6.46, 6.10.5

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available