CVE-2024-56548

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-12-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-53196 (ENISA EUVD) · GHSA-64p7-wm49-vgg4 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

hfsplus: don't query the device logical block size multiple times

Devices block sizes may change. One of these cases is a loop device by using ioctl LOOP_SET_BLOCK_SIZE.

While this may cause other issues like IO being rejected, in the case of hfsplus, it will allocate a block by using that size and potentially write out-of-bounds when hfsplus_read_wrapper calls hfsplus_submit_bio and the latter function reads a different io_size.

Using a new min_io_size initally set to sb_min_blocksize works for the purposes of the original fix, since it will be set to the max between HFSPLUS_SECTOR_SIZE and the first seen logical block size. We still use the max between HFSPLUS_SECTOR_SIZE and min_io_size in case the latter is not initialized.

Tested by mounting an hfsplus filesystem with loop block sizes 512, 1024 and 4096.

The produced KASAN report before the fix looks like this:

[ 419.944641] ================================================================== [ 419.945655] BUG: KASAN: slab-use-after-free in hfsplus_read_wrapper+0x659/0xa0a [ 419.946703] Read of size 2 at addr ffff88800721fc00 by task repro/10678 [ 419.947612] [ 419.947846] CPU: 0 UID: 0 PID: 10678 Comm: repro Not tainted 6.12.0-rc5-00008-gdf56e0f2f3ca #84 [ 419.949007] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014 [ 419.950035] Call Trace: [ 419.950384] [ 419.950676] dump_stack_lvl+0x57/0x78 [ 419.951212] ? hfsplus_read_wrapper+0x659/0xa0a [ 419.951830] print_report+0x14c/0x49e [ 419.952361] ? __virt_addr_valid+0x267/0x278 [ 419.952979] ? kmem_cache_debug_flags+0xc/0x1d [ 419.953561] ? hfsplus_read_wrapper+0x659/0xa0a [ 419.954231] kasan_report+0x89/0xb0 [ 419.954748] ? hfsplus_read_wrapper+0x659/0xa0a [ 419.955367] hfsplus_read_wrapper+0x659/0xa0a [ 419.955948] ? __pfx_hfsplus_read_wrapper+0x10/0x10 [ 419.956618] ? do_raw_spin_unlock+0x59/0x1a9 [ 419.957214] ? _raw_spin_unlock+0x1a/0x2e [ 419.957772] hfsplus_fill_super+0x348/0x1590 [ 419.958355] ? hlock_class+0x4c/0x109 [ 419.958867] ? __pfx_hfsplus_fill_super+0x10/0x10 [ 419.959499] ? __pfx_string+0x10/0x10 [ 419.960006] ? lock_acquire+0x3e2/0x454 [ 419.960532] ? bdev_name.constprop.0+0xce/0x243 [ 419.961129] ? __pfx_bdev_name.constprop.0+0x10/0x10 [ 419.961799] ? pointer+0x3f0/0x62f [ 419.962277] ? __pfx_pointer+0x10/0x10 [ 419.962761] ? vsnprintf+0x6c4/0xfba [ 419.963178] ? __pfx_vsnprintf+0x10/0x10 [ 419.963621] ? setup_bdev_super+0x376/0x3b3 [ 419.964029] ? snprintf+0x9d/0xd2 [ 419.964344] ? __pfx_snprintf+0x10/0x10 [ 419.964675] ? lock_acquired+0x45c/0x5e9 [ 419.965016] ? set_blocksize+0x139/0x1c1 [ 419.965381] ? sb_set_blocksize+0x6d/0xae [ 419.965742] ? __pfx_hfsplus_fill_super+0x10/0x10 [ 419.966179] mount_bdev+0x12f/0x1bf [ 419.966512] ? __pfx_mount_bdev+0x10/0x10 [ 419.966886] ? vfs_parse_fs_string+0xce/0x111 [ 419.967293] ? __pfx_vfs_parse_fs_string+0x10/0x10 [ 419.967702] ? __pfx_hfsplus_mount+0x10/0x10 [ 419.968073] legacy_get_tree+0x104/0x178 [ 419.968414] vfs_get_tree+0x86/0x296 [ 419.968751] path_mount+0xba3/0xd0b [ 419.969157] ? __pfx_path_mount+0x10/0x10 [ 419.969594] ? kmem_cache_free+0x1e2/0x260 [ 419.970311] do_mount+0x99/0xe0 [ 419.970630] ? __pfx_do_mount+0x10/0x10 [ 419.971008] __do_sys_mount+0x199/0x1c9 [ 419.971397] do_syscall_64+0xd0/0x135 [ 419.971761] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 419.972233] RIP: 0033:0x7c3cb812972e [ 419.972564] Code: 48 8b 0d f5 46 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c2 46 0d 00 f7 d8 64 89 01 48 [ 419.974371] RSP: 002b:00007ffe30632548 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5 [ 419.975048] RAX: ffffffffffffffda RBX: 00007ffe306328d8 RCX: 00007c3cb812972e [ 419.975701] RDX: 0000000020000000 RSI: 0000000020000c80 RDI: ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
16th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 27, 2024

Last Modified

August 5, 2026

Advisory Details (9)

Auto-updated Sep 21, 2026
Patch available.
Web page

hfsplus: don't query the device logical block size multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1c82587cb57687de3f18ab4b98a8850c789bedcf
Web page

hfsplus: don't query the device logical block size multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bfeecda050aa9376f642d5b2a71c4112cc6c8216
Web page

hfsplus: don't query the device logical block size multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2667c9b7b76efcbc7adbfea249892f20c313b0da
Web page

hfsplus: don't query the device logical block size multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/21900e8478126ff6afe3b66679f676e74d1f8830
Web page

hfsplus: don't query the device logical block size multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3d7bda75e1a6239db053c73acde17ca146317824
Web page

hfsplus: don't query the device logical block size multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/06cbfbb13ac88f4154c2eb4bc4176f9d10139847
Web page

hfsplus: don't query the device logical block size multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e8a2b1c1c2ea85e9a5a2d0c5a5a7e7c639feb866
Web page

hfsplus: don't query the device logical block size multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f57725bcc5816425e25218fdf5fb6923bc578cdf
Web page

hfsplus: don't query the device logical block size multiple times - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/baccb5e12577b7a9eff54ffba301fdaa0f3ee5a8

Vendor Advisories for CVE-2024-56548(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1044.48) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1028.30~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1020.21) @ noble2026-10-27ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1077.83~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-58.60~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1081.90~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1014.15) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1129.160) @ focal2026-10-27ubuntu
ubuntulinux-tools-raspi-hwe-18.04-edge (5.4.0.1129.142~18.04.1) @ bionic2026-10-27ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.278.284) @ xenial2026-10-27ubuntu
ubuntulinux-tools-azure (4.15.0.1197.212~14.04.1) @ trusty2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-10-27ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-10-27ubuntu
ubuntulinux-tools-kvm (5.15.0.1076.72) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-fips (5.15.0.1079.69) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.135.133) @ jammy2026-10-27ubuntu
ubuntulinux-tools-realtime (5.15.0.1080.83) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt (5.15.0.1033.33) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.211.206) @ focal2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (5.4.0.1140.149~18.04.1) @ bionic2026-10-27ubuntu
ubuntulinux-tools-gcp-fips (5.4.0.1145.87) @ focal2026-10-27ubuntu
ubuntulinux-tools-fips (5.4.0.1116.113) @ focal2026-10-27ubuntu
ubuntulinux-tools-aws-fips (5.4.0.1142.89) @ focal2026-10-27ubuntu
ubuntulinux-tools-aws-lts-20.04 (5.4.0.1142.139) @ focal2026-10-27ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.247.259~16.04.1) @ xenial2026-10-27ubuntu
ubuntulinux-tools-aws-edge (5.4.0.1142.152~18.04.1) @ bionic2026-10-27ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.278.312~14.04.1) @ trusty2026-10-27ubuntu
ubuntulinux-tools-iot (5.4.0.1048.46) @ focal2026-10-27ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.136.147~20.04.1) @ focal2026-10-27ubuntu
linuxKernel @ 4.19.325 (fixes >=3.1.0)—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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (44 versions)
  • every version up to 5.10.234-1: fixed in 5.10.234-1
—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1, 6.1.119-1~deb11u1
  • every version up to 6.1.128-1~deb11u1: fixed in 6.1.128-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (32 versions)
  • every version up to 6.1.123-1: fixed in 6.1.123-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.3-1: fixed in 6.12.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.3-1: fixed in 6.12.3-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 222 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 127 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  2. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  3. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  4. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  5. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  6. 2026-10-27 18:57 UTCEG score recompute
  7. 2026-10-27 18:57 UTCVendor advisory
  8. 2026-10-27 18:57 UTCGHSA enrichmentGHSA-64p7-wm49-vgg4 · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  10. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  11. 2026-10-25 16:55 UTCEG score recompute
  12. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  13. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  14. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  15. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  16. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  17. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  18. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  19. 2026-10-19 15:24 UTCEG score recompute
  20. 2026-10-19 15:24 UTCVendor advisory
  21. 2026-10-19 15:23 UTCGHSA enrichmentGHSA-64p7-wm49-vgg4 · GitHub severity HIGH · GitHub CVSS 7.8
  22. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  23. 2026-10-18 05:58 UTCEG score recompute
  24. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  25. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.2% · 14th percentile
Show 70 more
  1. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  2. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  3. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  4. 2026-10-12 17:37 UTCEG score recompute
  5. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  6. 2026-10-11 21:03 UTCEG score recompute
  7. 2026-10-11 15:55 UTCEG score recompute
  8. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  9. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  10. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  11. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  12. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  13. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  14. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  15. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  16. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  17. 2026-10-02 16:24 UTCEG score recompute
  18. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  19. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  20. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  21. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  22. 2026-09-26 22:41 UTCOSV refresh
  23. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  24. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  25. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  26. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  27. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  28. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  29. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  30. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  31. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  32. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  33. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  34. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  35. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  36. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  37. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  38. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  39. 2026-09-07 08:18 UTCOSV refresh
  40. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  41. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  42. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  43. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  44. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  45. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  46. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  47. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  48. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  49. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  50. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  51. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  52. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  53. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  54. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  55. 2026-08-20 18:01 UTCOSV refresh
  56. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  57. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  58. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  59. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  60. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  61. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  62. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  63. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  64. 2026-08-11 13:41 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  65. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  66. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  67. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  68. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  69. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  70. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.2% · 15th percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-56548?
CVE-2024-56548 is a high-severity vulnerability; its CVE record was published on December 27, 2024. In the Linux kernel, the following vulnerability has been resolved: hfsplus: don't query the device logical block size multiple times Devices block sizes may change. One of these cases is a loop device by using ioctl LOOP_SET_BLOCK_SIZE. While this may cause other issues like IO being rejected, in…
When was the CVE record for CVE-2024-56548 published?
The CVE record for CVE-2024-56548 was published on December 27, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2024-56548 actively exploited?
CVE-2024-56548 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-56548?
CVE-2024-56548 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-56548?
A fix for CVE-2024-56548 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-56548 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-56548?

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

Book a Demo →Browse All CVEs