Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-36928: s390/qeth: Fix kernel panic after setting hsuid

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 10cb803aff3b11fe0bd5f274fc1c231a43e88df6, 5.11, 5.15.159.

Low priority for now. Upgrade to Linux Linux 10cb803aff3b11fe0bd5f274fc1c231a43e88df6, 5.11, 5.15.159 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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---

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
May 30, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 13th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-36928

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.10.190 and later · before 5.11
  • linux linux kernel5.15.126 and later · before 5.15.159
  • linux linux kernel6.1.45 and later · before 6.1.91
  • linux linux kernel6.4.10 and later · before 6.6.31
  • linux linux kernel6.7 and later · before 6.8.10
  • linux linux kernel6.9

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • c33d5a5c5b2c79326190885040f1643793c67b29, 29d6fe395087710280f8e11d4ae79569c4cb14b7, 6.5affected
    • 64e3affee2881bb22df7ce45dd1f1fd7990e382b and later · before 8792b557eb50b986f2496156d486d0c7c85a1524affected · git
    • 86818409f989fee29c38528ed8fb085655603356 and later · before 10cb803aff3b11fe0bd5f274fc1c231a43e88df6affected · git
    • 1cfef80d4c2b2c599189f36f36320b205d9447d9 and later · before e28dd1e1bf3ebb52cdb877fb359e8978a51576e3affected · git
    • 1cfef80d4c2b2c599189f36f36320b205d9447d9 and later · before eae0aec245712c52a3ce9c05575b541a9eef5282affected · git
    • 1cfef80d4c2b2c599189f36f36320b205d9447d9 and later · before 8a2e4d37afb8500b276e5ee903dee06f50ab0494affected · git
    • 5.15.126 and later · before 5.15.159affected · semver
    • 6.1.45 and later · before 6.1.91affected · semver
    • 5.10.190 and later · before 5.11affected · semver
    • 6.4.10 and later · before 6.5affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.94-16.1.94-1
Debian:13linuxbefore 6.8.11-16.8.11-1
Red Hat:rhel_eus:9.2::appstreambpftool-debuginfobefore 0:7.0.0-284.95.1.el9_20:7.0.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-debug-develbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-debuginfobefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-develbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debug-debuginfobefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debug-develbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfobefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-develbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-devel-matchedbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-docbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-tools-debuginfobefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-zfcpdump-develbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-zfcpdump-devel-matchedbefore 0:5.14.0-284.95.1.el9_20:5.14.0-284.95.1.el9_2

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-36925May 30, 2024 · swiotlb: initialise restricted pool list_head when SWIOTLB_DYNAMIC=y
    22Monitor
  • ← EarlierCVE-2024-36926May 30, 2024 · powerpc/pseries/iommu: LPAR panics during boot up with a frozen PE
    22Monitor
  • Later →CVE-2024-36930May 30, 2024 · spi: fix null pointer dereference within spi_sync
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux10cb803aff3b11fe0bd5f274fc1c231a43e88df6Vendor (CNA)
Linux Linux5.11Vendor (CNA)
Linux Linux5.15.159Vendor (CNA)
Linux Linux6.1.91Vendor (CNA)
Linux Linux6.5Vendor (CNA)
Linux Linux8792b557eb50b986f2496156d486d0c7c85a1524Vendor (CNA)
Linux Linux8a2e4d37afb8500b276e5ee903dee06f50ab0494Vendor (CNA)
Linux Linuxe28dd1e1bf3ebb52cdb877fb359e8978a51576e3Vendor (CNA)
Linux Linuxeae0aec245712c52a3ce9c05575b541a9eef5282Vendor (CNA)
debian:linux6.1.94-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-476 · NULL Pointer Dereference

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records