CVE-2024-44976

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2024-09-04. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

ata: pata_macio: Fix DMA table overflow

Kolbjørn and Jonáš reported that their 32-bit PowerMacs were crashing in pata-macio since commit 09fe2bfa6b83 ("ata: pata_macio: Fix max_segment_size with PAGE_SIZE == 64K").

For example:

kernel BUG at drivers/ata/pata_macio.c:544! Oops: Exception in kernel mode, sig: 5 [#1] BE PAGE_SIZE=4K MMU=Hash SMP NR_CPUS=2 DEBUG_PAGEALLOC PowerMac ... NIP pata_macio_qc_prep+0xf4/0x190 LR pata_macio_qc_prep+0xfc/0x190 Call Trace: 0xc1421660 (unreliable) ata_qc_issue+0x14c/0x2d4 __ata_scsi_queuecmd+0x200/0x53c ata_scsi_queuecmd+0x50/0xe0 scsi_queue_rq+0x788/0xb1c __blk_mq_issue_directly+0x58/0xf4 blk_mq_plug_issue_direct+0x8c/0x1b4 blk_mq_flush_plug_list.part.0+0x584/0x5e0 __blk_flush_plug+0xf8/0x194 __submit_bio+0x1b8/0x2e0 submit_bio_noacct_nocheck+0x230/0x304 btrfs_work_helper+0x200/0x338 process_one_work+0x1a8/0x338 worker_thread+0x364/0x4c0 kthread+0x100/0x104 start_kernel_thread+0x10/0x14

That commit increased max_segment_size to 64KB, with the justification that the SCSI core was already using that size when PAGE_SIZE == 64KB, and that there was existing logic to split over-sized requests.

However with a sufficiently large request, the splitting logic causes each sg to be split into two commands in the DMA table, leading to overflow of the DMA table, triggering the BUG_ON().

With default settings the bug doesn't trigger, because the request size is limited by max_sectors_kb == 1280, however max_sectors_kb can be increased, and apparently some distros do that by default using udev rules.

Fix the bug for 4KB kernels by reverting to the old max_segment_size.

For 64KB kernels the sg_tablesize needs to be halved, to allow for the possibility that each sg will be split into two.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

September 4, 2024

Last Modified

October 10, 2024

References (2)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.10.7—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.10.7-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.10.7-1—

Data Freshness Timeline

(refreshed 10× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 163 total refreshes for this CVE.

  1. 2026-09-22 14:47 UTCEPSS rescore
  2. 2026-09-21 20:32 UTCEPSS rescore
  3. 2026-09-20 20:14 UTCEPSS rescore
  4. 2026-09-20 20:14 UTCEPSS rescore
  5. 2026-09-20 08:13 UTCOSV refresh
  6. 2026-09-19 15:40 UTCEPSS rescore
  7. 2026-09-18 19:26 UTCEPSS rescore
  8. 2026-09-18 19:26 UTCEPSS rescore
  9. 2026-09-16 14:06 UTCEPSS rescore
  10. 2026-09-16 05:12 UTCEPSS rescore
  11. 2026-09-15 03:08 UTCEPSS rescore
  12. 2026-09-15 03:08 UTCEPSS rescore
  13. 2026-09-13 16:45 UTCEPSS rescore
  14. 2026-09-12 14:59 UTCEPSS rescore
  15. 2026-09-11 14:51 UTCEPSS rescore
  16. 2026-09-11 09:35 UTCEPSS rescore
  17. 2026-09-08 21:58 UTCEPSS rescore
  18. 2026-09-07 16:00 UTCEPSS rescore
  19. 2026-09-06 13:46 UTCEPSS rescore
  20. 2026-09-06 13:46 UTCEPSS rescore
  21. 2026-09-05 15:27 UTCEPSS rescore
  22. 2026-09-04 13:59 UTCEPSS rescore
  23. 2026-09-04 05:05 UTCEPSS rescore
  24. 2026-09-02 14:10 UTCEPSS rescore
  25. 2026-09-01 13:52 UTCEPSS rescore
Show 75 more
  1. 2026-09-01 11:36 UTCOSV refresh
  2. 2026-08-30 19:16 UTCEPSS rescore
  3. 2026-08-28 21:39 UTCEPSS rescore
  4. 2026-08-27 14:23 UTCEPSS rescore
  5. 2026-08-25 13:47 UTCEPSS rescore
  6. 2026-08-24 14:15 UTCEPSS rescore
  7. 2026-08-23 00:18 UTCEPSS rescore
  8. 2026-08-21 23:47 UTCEPSS rescore
  9. 2026-08-19 17:02 UTCEPSS rescore
  10. 2026-08-18 13:46 UTCEPSS rescore
  11. 2026-08-16 14:54 UTCEPSS rescore
  12. 2026-08-16 02:13 UTCEPSS rescore
  13. 2026-08-15 11:07 UTCOSV refresh
  14. 2026-08-15 01:28 UTCEPSS rescore
  15. 2026-08-13 21:59 UTCEPSS rescore
  16. 2026-08-12 13:49 UTCEPSS rescore
  17. 2026-08-11 13:40 UTCEPSS rescore
  18. 2026-08-10 23:58 UTCEPSS rescore
  19. 2026-08-09 13:45 UTCEPSS rescore
  20. 2026-08-08 16:35 UTCEPSS rescore
  21. 2026-08-07 16:25 UTCEPSS rescore
  22. 2026-08-06 13:45 UTCEPSS rescore
  23. 2026-08-05 19:16 UTCEPSS rescore
  24. 2026-08-04 15:08 UTCEPSS rescore
  25. 2026-08-04 10:36 UTCEPSS rescore
  26. 2026-08-03 10:34 UTCEPSS rescore
  27. 2026-08-02 02:25 UTCEPSS rescore
  28. 2026-08-01 04:14 UTCEPSS rescore
  29. 2026-07-30 23:51 UTCOSV refresh
  30. 2026-07-30 16:26 UTCEPSS rescore
  31. 2026-07-30 01:29 UTCEPSS rescore
  32. 2026-07-28 15:34 UTCEPSS rescore
  33. 2026-07-27 14:11 UTCEPSS rescore
  34. 2026-07-26 14:53 UTCEPSS rescore
  35. 2026-07-26 14:53 UTCEPSS rescore
  36. 2026-07-25 14:16 UTCEPSS rescore
  37. 2026-07-23 14:17 UTCEPSS rescore
  38. 2026-07-23 02:40 UTCEG score recompute
  39. 2026-07-22 14:07 UTCEPSS rescore
  40. 2026-07-21 15:23 UTCEPSS rescore
  41. 2026-07-21 15:23 UTCEPSS rescore
  42. 2026-07-20 17:06 UTCEPSS rescore
  43. 2026-07-19 14:30 UTCEPSS rescore
  44. 2026-07-19 14:30 UTCEPSS rescore
  45. 2026-07-19 02:28 UTCEPSS rescore
  46. 2026-07-19 02:28 UTCEPSS rescore
  47. 2026-07-18 10:03 UTCEPSS rescore
  48. 2026-07-18 10:03 UTCEPSS rescore
  49. 2026-07-16 17:02 UTCEPSS rescore
  50. 2026-07-15 16:56 UTCEPSS rescore
  51. 2026-07-15 16:56 UTCEPSS rescore
  52. 2026-07-15 01:59 UTCEPSS rescore
  53. 2026-07-15 01:59 UTCEPSS rescore
  54. 2026-07-13 22:29 UTCEPSS rescore
  55. 2026-07-13 08:38 UTCOSV refresh
  56. 2026-07-13 06:12 UTCEPSS rescore
  57. 2026-07-12 05:45 UTCEPSS rescore
  58. 2026-07-12 05:45 UTCEPSS rescore
  59. 2026-07-11 08:26 UTCEPSS rescore
  60. 2026-07-09 19:09 UTCEPSS rescore
  61. 2026-07-09 19:09 UTCEPSS rescore
  62. 2026-07-08 15:14 UTCEPSS rescore
  63. 2026-07-07 13:45 UTCEPSS rescore
  64. 2026-07-06 16:26 UTCEPSS rescore
  65. 2026-07-06 02:22 UTCEPSS rescore
  66. 2026-07-06 02:22 UTCEPSS rescore
  67. 2026-07-04 06:30 UTCEPSS rescore
  68. 2026-07-01 15:05 UTCEPSS rescore
  69. 2026-06-30 23:21 UTCEPSS rescore
  70. 2026-06-30 23:21 UTCEPSS rescore
  71. 2026-06-29 14:05 UTCEPSS rescore
  72. 2026-06-28 14:07 UTCEPSS rescore
  73. 2026-06-28 14:06 UTCEPSS rescore
  74. 2026-06-28 04:55 UTCEPSS rescore
  75. 2026-06-28 04:55 UTCEPSS rescore

Related CVEs(same product)

Frequently asked(5)

What is CVE-2024-44976?
CVE-2024-44976 is a medium vulnerability published on September 4, 2024. In the Linux kernel, the following vulnerability has been resolved: ata: pata_macio: Fix DMA table overflow Kolbjørn and Jonáš reported that their 32-bit PowerMacs were crashing in pata-macio since commit 09fe2bfa6b83 ("ata: pata_macio: Fix maxsegmentsize with PAGE_SIZE == 64K"). For example:…
When was CVE-2024-44976 disclosed?
CVE-2024-44976 was first published in the National Vulnerability Database on September 4, 2024, with the most recent update on October 10, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-44976 actively exploited?
CVE-2024-44976 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.4% of all scored CVEs.
What is the CVSS score of CVE-2024-44976?
CVE-2024-44976 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-44976?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-44976, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-44976

Explore →

Is Your Infrastructure Affected by CVE-2024-44976?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs