CVE-2024-36928

MEDIUMNVD 4.44.4
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.4 under NVD CVSS v3. EPSS exploit probability: 0.2% (12th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week
4.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

s390/qeth: Fix kernel panic after setting hsuid

Symptom: When the hsuid attribute is set for the first time on an IQD Layer3 device while the corresponding network interface is already UP, the kernel will try to execute a napi function pointer that is NULL.

Example: --------------------------------------------------------------------------- [ 2057.572696] illegal operation: 0001 ilc:1 [#1] SMP [ 2057.572702] Modules linked in: af_iucv qeth_l3 zfcp scsi_transport_fc sunrpc nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nf_tables_set nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables libcrc32c nfnetlink ghash_s390 prng xts aes_s390 des_s390 de s_generic sha3_512_s390 sha3_256_s390 sha512_s390 vfio_ccw vfio_mdev mdev vfio_iommu_type1 eadm_sch vfio ext4 mbcache jbd2 qeth_l2 bridge stp llc dasd_eckd_mod qeth dasd_mod qdio ccwgroup pkey zcrypt [ 2057.572739] CPU: 6 PID: 60182 Comm: stress_client Kdump: loaded Not tainted 4.18.0-541.el8.s390x #1 [ 2057.572742] Hardware name: IBM 3931 A01 704 (LPAR) [ 2057.572744] Krnl PSW : 0704f00180000000 0000000000000002 (0x2) [ 2057.572748] R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:3 PM:0 RI:0 EA:3 [ 2057.572751] Krnl GPRS: 0000000000000004 0000000000000000 00000000a3b008d8 0000000000000000 [ 2057.572754] 00000000a3b008d8 cb923a29c779abc5 0000000000000000 00000000814cfd80 [ 2057.572756] 000000000000012c 0000000000000000 00000000a3b008d8 00000000a3b008d8 [ 2057.572758] 00000000bab6d500 00000000814cfd80 0000000091317e46 00000000814cfc68 [ 2057.572762] Krnl Code:#0000000000000000: 0000 illegal >0000000000000002: 0000 illegal 0000000000000004: 0000 illegal 0000000000000006: 0000 illegal 0000000000000008: 0000 illegal 000000000000000a: 0000 illegal 000000000000000c: 0000 illegal 000000000000000e: 0000 illegal [ 2057.572800] Call Trace: [ 2057.572801] ([<00000000ec639700>] 0xec639700) [ 2057.572803] [<00000000913183e2>] net_rx_action+0x2ba/0x398 [ 2057.572809] [<0000000091515f76>] __do_softirq+0x11e/0x3a0 [ 2057.572813] [<0000000090ce160c>] do_softirq_own_stack+0x3c/0x58 [ 2057.572817] ([<0000000090d2cbd6>] do_softirq.part.1+0x56/0x60) [ 2057.572822] [<0000000090d2cc60>] __local_bh_enable_ip+0x80/0x98 [ 2057.572825] [<0000000091314706>] __dev_queue_xmit+0x2be/0xd70 [ 2057.572827] [<000003ff803dd6d6>] afiucv_hs_send+0x24e/0x300 [af_iucv] [ 2057.572830] [<000003ff803dd88a>] iucv_send_ctrl+0x102/0x138 [af_iucv] [ 2057.572833] [<000003ff803de72a>] iucv_sock_connect+0x37a/0x468 [af_iucv] [ 2057.572835] [<00000000912e7e90>] __sys_connect+0xa0/0xd8 [ 2057.572839] [<00000000912e9580>] sys_socketcall+0x228/0x348 [ 2057.572841] [<0000000091514e1a>] system_call+0x2a6/0x2c8 [ 2057.572843] Last Breaking-Event-Address: [ 2057.572844] [<0000000091317e44>] __napi_poll+0x4c/0x1d8 [ 2057.572846] [ 2057.572847] Kernel panic - not syncing: Fatal exception in interrupt -------------------------------------------------------------------------------------------

Analysis: There is one napi structure per out_q: card->qdio.out_qs[i].napi The napi.poll functions are set during qeth_open().

Since commit 1cfef80d4c2b ("s390/qeth: Don't call dev_close/dev_open (DOWN/UP)") qeth_set_offline()/qeth_set_online() no longer call dev_close()/ dev_open(). So if qeth_free_qdio_queues() cleared card->qdio.out_qs[i].napi.poll while the network interface was UP and the card was offline, they are not set again.

Reproduction: chzdev -e $devno layer2=0 ip link set dev $network_interface up echo 0 > /sys/bus/ccw ---truncated---

CVSS v3
4.4
EG Score
4.4MEDIUMmedium confidence
EG Risk
20
EG Risk 20/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)
Severity44% × 45%
Impact severity (EG Severity): CVSS 4.4 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
12th
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 (4.4): severity, escalated by confirmed exploitation. This CVE's 4.4 is its impact severity (EG Severity), not escalated.

EG Severity
4.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

May 30, 2024

Last Modified

August 5, 2026

Patch Availability(16)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (498 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.94-1~bpo11+1 (23 versions)
  • every version up to 6.1.94-1: fixed in 6.1.94-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.11-1: fixed in 6.8.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.11-1: fixed in 6.8.11-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(11)

Data Freshness Timeline

(refreshed 8× in last 7d / 35× 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 93 of 201 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. 7 repeat rows among the latest 100 are merged into the row they repeat. The 108 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-36928?
CVE-2024-36928 is a medium-severity vulnerability; its CVE record was published on May 30, 2024. In the Linux kernel, the following vulnerability has been resolved: s390/qeth: Fix kernel panic after setting hsuid Symptom: When the hsuid attribute is set for the first time on an IQD Layer3 device while the corresponding network interface is already UP, the kernel will try to execute a napi…
When was the CVE record for CVE-2024-36928 published?
The CVE record for CVE-2024-36928 was published on May 30, 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-36928 actively exploited?
CVE-2024-36928 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-36928?
CVE-2024-36928 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2024-36928?
A fix for CVE-2024-36928 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-36928 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-36928

Explore →

Is Your Infrastructure Affected by CVE-2024-36928?

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