BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-36928High confidence

s390/qeth: Fix kernel panic after setting hsuid

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.23% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

17 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 13 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.8.11-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.94-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.8.11-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.8.11-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.8Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2024-36928 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: s390/qeth: Fix kernel panic after setting hsuid
880 fixed

The vendor explicitly identifies these products or versions as containing the fix.

  • bpftool-debuginfo-0:7.0.0-284.95.1.el9_2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)
  • bpftool-debuginfo-0:7.0.0-284.95.1.el9_2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)
  • bpftool-debuginfo-0:7.0.0-284.95.1.el9_2.s390x as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)
  • bpftool-debuginfo-0:7.0.0-284.95.1.el9_2.x86_64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)
  • kernel-64k-debug-debuginfo-0:5.14.0-284.95.1.el9_2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)
  • kernel-64k-debug-devel-0:5.14.0-284.95.1.el9_2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)
  • kernel-64k-debug-devel-matched-0:5.14.0-284.95.1.el9_2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)
  • kernel-64k-debuginfo-0:5.14.0-284.95.1.el9_2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)
  • kernel-64k-devel-0:5.14.0-284.95.1.el9_2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)
  • kernel-64k-devel-matched-0:5.14.0-284.95.1.el9_2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)
  • kernel-debug-debuginfo-0:5.14.0-284.95.1.el9_2.aarch64 as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)
  • kernel-debug-debuginfo-0:5.14.0-284.95.1.el9_2.ppc64le as a component of Red Hat Enterprise Linux AppStream EUS (v.9.2)
Summary
A flaw was found in the Linux kernel's s390/qeth component. A local attacker with privileges to manage network devices could trigger a kernel panic by setting the hsuid attribute on an IQD Layer3 device while its network interface is active. This occurs because the kernel attempts to execute a null function pointer. Successful exploitation leads to a Denial of Service (DoS) for the system.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-36278

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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

What

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

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → NULL Pointer Dereference → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-476
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2024-1259Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und unspezifischen Angriff

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder einen unspezifischen Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240605Security Bulletin 05 Jun 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 05 Jun 2024, published on 5 June 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1165Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-36904 Référence CVE CVE-2024-36905 https://www.cve.org/CVERecord?id=CVE-2024-36905 Référence CVE CVE-2024-36917 https://www.cve.org/CVERecord?id=CVE-2024-36917 Référence CVE CVE-2024-36919 https://www.cve.org/CVERecord?id=CVE-2024-36919 Référence CVE CVE-2024-36920 https://www.cve.org/CVERecord?id=CVE-2024-36920 Référence CVE CVE-2024-36921 https://www.cve.org/CVERecord?id=CVE-2024-36921 Référence CVE CVE-2024-36922 https://www.cve.org/CVERecord?id=CVE-2024-36922 Référence CVE CVE-2024-36924 https://www.cve.org/CVERecord?id=CVE-2024-36924 Référence CVE CVE-2024-36927 https://www.cve.org/CVERecord?id=CVE-2024-36927 Référence CVE CVE-2024-36928 https://www.cve.org/CVERecord?id=CVE-2024-36928 Référence CVE CVE-2024-36929 https://www.cve.org/CVERecord?id=CVE-2024-36929 Référence CVE CVE-2024-36933 https://www.cve.org/CVERecord?id=CVE-2024-36933 Référence CVE CVE-2024-36939 https://www.cve.org/CVERecord?id=CVE-2024-36939 Référence CVE CVE-2024-36940 https://www.cve.org/CVERecord?id=CVE-2024-36940 Référence CVE CVE-2024-36941 https://www.cve.org/CVERecord?id=CVE-2024-36941 Référence CVE CVE-2024-36945 https://www.cve.org/CVERecord?id=CVE-2024-36945 Référence CVE CVE-2024-36950 https://www.cve.org/CVERecord?id=CVE-2024-36950 Référence CVE CVE-2024-36952 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1050Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2023-52811 Référence CVE CVE-2023-52881 https://www.cve.org/CVERecord?id=CVE-2023-52881 Référence CVE CVE-2024-26601 https://www.cve.org/CVERecord?id=CVE-2024-26601 Référence CVE CVE-2024-26615 https://www.cve.org/CVERecord?id=CVE-2024-26615 Référence CVE CVE-2024-26686 https://www.cve.org/CVERecord?id=CVE-2024-26686 Référence CVE CVE-2024-26704 https://www.cve.org/CVERecord?id=CVE-2024-26704 Référence CVE CVE-2024-26984 https://www.cve.org/CVERecord?id=CVE-2024-26984 Référence CVE CVE-2024-27399 https://www.cve.org/CVERecord?id=CVE-2024-27399 Référence CVE CVE-2024-36920 https://www.cve.org/CVERecord?id=CVE-2024-36920 Référence CVE CVE-2024-36928 https://www.cve.org/CVERecord?id=CVE-2024-36928 Référence CVE CVE-2024-36960 https://www.cve.org/CVERecord?id=CVE-2024-36960 Référence CVE CVE-2024-37356 https://www.cve.org/CVERecord?id=CVE-2024-37356 Référence CVE CVE-2024-38384 https://www.cve.org/CVERecord?id=CVE-2024-38384 Référence CVE CVE-2024-38541 https://www.cve.org/CVERecord?id=CVE-2024-38541 Référence CVE CVE-2024-38555 https://www.cve.org/CVERecord?id=CVE-2024-38555 Référence CVE CVE-2024-39507 https://www.cve.org/CVERecord?id=CVE-2024-39507 Référence CVE CVE-2024-40988 https://www.cve.org/CVERecord?id=CVE-2024-40988 Référence CVE CVE-2024-40997 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0799Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-36889 Référence CVE CVE-2024-36894 https://www.cve.org/CVERecord?id=CVE-2024-36894 Référence CVE CVE-2024-36901 https://www.cve.org/CVERecord?id=CVE-2024-36901 Référence CVE CVE-2024-36902 https://www.cve.org/CVERecord?id=CVE-2024-36902 Référence CVE CVE-2024-36904 https://www.cve.org/CVERecord?id=CVE-2024-36904 Référence CVE CVE-2024-36905 https://www.cve.org/CVERecord?id=CVE-2024-36905 Référence CVE CVE-2024-36906 https://www.cve.org/CVERecord?id=CVE-2024-36906 Référence CVE CVE-2024-36916 https://www.cve.org/CVERecord?id=CVE-2024-36916 Référence CVE CVE-2024-36919 https://www.cve.org/CVERecord?id=CVE-2024-36919 Référence CVE CVE-2024-36928 https://www.cve.org/CVERecord?id=CVE-2024-36928 Référence CVE CVE-2024-36929 https://www.cve.org/CVERecord?id=CVE-2024-36929 Référence CVE CVE-2024-36931 https://www.cve.org/CVERecord?id=CVE-2024-36931 Référence CVE CVE-2024-36933 https://www.cve.org/CVERecord?id=CVE-2024-36933 Référence CVE CVE-2024-36934 https://www.cve.org/CVERecord?id=CVE-2024-36934 Référence CVE CVE-2024-36937 https://www.cve.org/CVERecord?id=CVE-2024-36937 Référence CVE CVE-2024-36938 https://www.cve.org/CVERecord?id=CVE-2024-36938 Référence CVE CVE-2024-36939 https://www.cve.org/CVERecord?id=CVE-2024-36939 Référence CVE CVE-2024-36940 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0717Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-36916 Référence CVE CVE-2024-36917 https://www.cve.org/CVERecord?id=CVE-2024-36917 Référence CVE CVE-2024-36918 https://www.cve.org/CVERecord?id=CVE-2024-36918 Référence CVE CVE-2024-36919 https://www.cve.org/CVERecord?id=CVE-2024-36919 Référence CVE CVE-2024-36921 https://www.cve.org/CVERecord?id=CVE-2024-36921 Référence CVE CVE-2024-36922 https://www.cve.org/CVERecord?id=CVE-2024-36922 Référence CVE CVE-2024-36923 https://www.cve.org/CVERecord?id=CVE-2024-36923 Référence CVE CVE-2024-36924 https://www.cve.org/CVERecord?id=CVE-2024-36924 Référence CVE CVE-2024-36926 https://www.cve.org/CVERecord?id=CVE-2024-36926 Référence CVE CVE-2024-36928 https://www.cve.org/CVERecord?id=CVE-2024-36928 Référence CVE CVE-2024-36930 https://www.cve.org/CVERecord?id=CVE-2024-36930 Référence CVE CVE-2024-36931 https://www.cve.org/CVERecord?id=CVE-2024-36931 Référence CVE CVE-2024-36934 https://www.cve.org/CVERecord?id=CVE-2024-36934 Référence CVE CVE-2024-36935 https://www.cve.org/CVERecord?id=CVE-2024-36935 Référence CVE CVE-2024-36936 https://www.cve.org/CVERecord?id=CVE-2024-36936 Référence CVE CVE-2024-36937 https://www.cve.org/CVERecord?id=CVE-2024-36937 Référence CVE CVE-2024-36938 https://www.cve.org/CVERecord?id=CVE-2024-36938 Référence CVE CVE-2024-36939 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0716Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-36886 Référence CVE CVE-2024-36889 https://www.cve.org/CVERecord?id=CVE-2024-36889 Référence CVE CVE-2024-36901 https://www.cve.org/CVERecord?id=CVE-2024-36901 Référence CVE CVE-2024-36902 https://www.cve.org/CVERecord?id=CVE-2024-36902 Référence CVE CVE-2024-36904 https://www.cve.org/CVERecord?id=CVE-2024-36904 Référence CVE CVE-2024-36905 https://www.cve.org/CVERecord?id=CVE-2024-36905 Référence CVE CVE-2024-36906 https://www.cve.org/CVERecord?id=CVE-2024-36906 Référence CVE CVE-2024-36916 https://www.cve.org/CVERecord?id=CVE-2024-36916 Référence CVE CVE-2024-36919 https://www.cve.org/CVERecord?id=CVE-2024-36919 Référence CVE CVE-2024-36928 https://www.cve.org/CVERecord?id=CVE-2024-36928 Référence CVE CVE-2024-36929 https://www.cve.org/CVERecord?id=CVE-2024-36929 Référence CVE CVE-2024-36931 https://www.cve.org/CVERecord?id=CVE-2024-36931 Référence CVE CVE-2024-36933 https://www.cve.org/CVERecord?id=CVE-2024-36933 Référence CVE CVE-2024-36934 https://www.cve.org/CVERecord?id=CVE-2024-36934 Référence CVE CVE-2024-36937 https://www.cve.org/CVERecord?id=CVE-2024-36937 Référence CVE CVE-2024-36938 https://www.cve.org/CVERecord?id=CVE-2024-36938 Référence CVE CVE-2024-36939 https://www.cve.org/CVERecord?id=CVE-2024-36939 Référence CVE CVE-2024-36940 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0694Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-36919 Référence CVE CVE-2024-36920 https://www.cve.org/CVERecord?id=CVE-2024-36920 Référence CVE CVE-2024-36921 https://www.cve.org/CVERecord?id=CVE-2024-36921 Référence CVE CVE-2024-36922 https://www.cve.org/CVERecord?id=CVE-2024-36922 Référence CVE CVE-2024-36923 https://www.cve.org/CVERecord?id=CVE-2024-36923 Référence CVE CVE-2024-36924 https://www.cve.org/CVERecord?id=CVE-2024-36924 Référence CVE CVE-2024-36925 https://www.cve.org/CVERecord?id=CVE-2024-36925 Référence CVE CVE-2024-36926 https://www.cve.org/CVERecord?id=CVE-2024-36926 Référence CVE CVE-2024-36927 https://www.cve.org/CVERecord?id=CVE-2024-36927 Référence CVE CVE-2024-36928 https://www.cve.org/CVERecord?id=CVE-2024-36928 Référence CVE CVE-2024-36929 https://www.cve.org/CVERecord?id=CVE-2024-36929 Référence CVE CVE-2024-36930 https://www.cve.org/CVERecord?id=CVE-2024-36930 Référence CVE CVE-2024-36931 https://www.cve.org/CVERecord?id=CVE-2024-36931 Référence CVE CVE-2024-36932 https://www.cve.org/CVERecord?id=CVE-2024-36932 Référence CVE CVE-2024-36933 https://www.cve.org/CVERecord?id=CVE-2024-36933 Référence CVE CVE-2024-36934 https://www.cve.org/CVERecord?id=CVE-2024-36934 Référence CVE CVE-2024-36935 https://www.cve.org/CVERecord?id=CVE-2024-36935 Référence CVE CVE-2024-36936 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0667Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-36919 Référence CVE CVE-2024-36920 https://www.cve.org/CVERecord?id=CVE-2024-36920 Référence CVE CVE-2024-36921 https://www.cve.org/CVERecord?id=CVE-2024-36921 Référence CVE CVE-2024-36922 https://www.cve.org/CVERecord?id=CVE-2024-36922 Référence CVE CVE-2024-36923 https://www.cve.org/CVERecord?id=CVE-2024-36923 Référence CVE CVE-2024-36924 https://www.cve.org/CVERecord?id=CVE-2024-36924 Référence CVE CVE-2024-36925 https://www.cve.org/CVERecord?id=CVE-2024-36925 Référence CVE CVE-2024-36926 https://www.cve.org/CVERecord?id=CVE-2024-36926 Référence CVE CVE-2024-36927 https://www.cve.org/CVERecord?id=CVE-2024-36927 Référence CVE CVE-2024-36928 https://www.cve.org/CVERecord?id=CVE-2024-36928 Référence CVE CVE-2024-36929 https://www.cve.org/CVERecord?id=CVE-2024-36929 Référence CVE CVE-2024-36930 https://www.cve.org/CVERecord?id=CVE-2024-36930 Référence CVE CVE-2024-36931 https://www.cve.org/CVERecord?id=CVE-2024-36931 Référence CVE CVE-2024-36932 https://www.cve.org/CVERecord?id=CVE-2024-36932 Référence CVE CVE-2024-36933 https://www.cve.org/CVERecord?id=CVE-2024-36933 Référence CVE CVE-2024-36934 https://www.cve.org/CVERecord?id=CVE-2024-36934 Référence CVE CVE-2024-36935 https://www.cve.org/CVERecord?id=CVE-2024-36935 Référence CVE CVE-2024-36936 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0526Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-36896 Référence CVE CVE-2024-36897 https://www.cve.org/CVERecord?id=CVE-2024-36897 Référence CVE CVE-2024-36898 https://www.cve.org/CVERecord?id=CVE-2024-36898 Référence CVE CVE-2024-36906 https://www.cve.org/CVERecord?id=CVE-2024-36906 Référence CVE CVE-2024-36918 https://www.cve.org/CVERecord?id=CVE-2024-36918 Référence CVE CVE-2024-36921 https://www.cve.org/CVERecord?id=CVE-2024-36921 Référence CVE CVE-2024-36922 https://www.cve.org/CVERecord?id=CVE-2024-36922 Référence CVE CVE-2024-36924 https://www.cve.org/CVERecord?id=CVE-2024-36924 Référence CVE CVE-2024-36926 https://www.cve.org/CVERecord?id=CVE-2024-36926 Référence CVE CVE-2024-36928 https://www.cve.org/CVERecord?id=CVE-2024-36928 Référence CVE CVE-2024-36930 https://www.cve.org/CVERecord?id=CVE-2024-36930 Référence CVE CVE-2024-36931 https://www.cve.org/CVERecord?id=CVE-2024-36931 Référence CVE CVE-2024-36936 https://www.cve.org/CVERecord?id=CVE-2024-36936 Référence CVE CVE-2024-36938 https://www.cve.org/CVERecord?id=CVE-2024-36938 Référence CVE CVE-2024-36940 https://www.cve.org/CVERecord?id=CVE-2024-36940 Référence CVE CVE-2024-36941 https://www.cve.org/CVERecord?id=CVE-2024-36941 Référence CVE CVE-2024-36942 https://www.cve.org/CVERecord?id=CVE-2024-36942 Référence CVE CVE-2024-36944 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0496Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-36032 Référence CVE CVE-2024-36880 https://www.cve.org/CVERecord?id=CVE-2024-36880 Référence CVE CVE-2024-36893 https://www.cve.org/CVERecord?id=CVE-2024-36893 Référence CVE CVE-2024-36896 https://www.cve.org/CVERecord?id=CVE-2024-36896 Référence CVE CVE-2024-36897 https://www.cve.org/CVERecord?id=CVE-2024-36897 Référence CVE CVE-2024-36906 https://www.cve.org/CVERecord?id=CVE-2024-36906 Référence CVE CVE-2024-36918 https://www.cve.org/CVERecord?id=CVE-2024-36918 Référence CVE CVE-2024-36924 https://www.cve.org/CVERecord?id=CVE-2024-36924 Référence CVE CVE-2024-36926 https://www.cve.org/CVERecord?id=CVE-2024-36926 Référence CVE CVE-2024-36928 https://www.cve.org/CVERecord?id=CVE-2024-36928 Référence CVE CVE-2024-36931 https://www.cve.org/CVERecord?id=CVE-2024-36931 Référence CVE CVE-2024-36938 https://www.cve.org/CVERecord?id=CVE-2024-36938 Référence CVE CVE-2024-36940 https://www.cve.org/CVERecord?id=CVE-2024-36940 Référence CVE CVE-2024-36941 https://www.cve.org/CVERecord?id=CVE-2024-36941 Référence CVE CVE-2024-36942 https://www.cve.org/CVERecord?id=CVE-2024-36942 Référence CVE CVE-2024-36944 https://www.cve.org/CVERecord?id=CVE-2024-36944 Référence CVE CVE-2024-36947 https://www.cve.org/CVERecord?id=CVE-2024-36947 Référence CVE CVE-2024-36950 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-021542Linux の Linux Kernel における NULL ポインタデリファレンスに関する脆弱性

Linux の Linux Kernel には、NULL ポインタデリファレンスに関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Linux: 64e3affee2881bb22df7ce45dd1f1fd7990e382b < 8792b557eb50b986f2496156d486d0c7c85a1524, 86818409f989fee29c38528ed8fb085655603356 < 10cb803aff3b11fe0bd5f274fc1c231a43e88df6, 1cfef80d4c2b2c599189f36f36320b205d9447d9 < e28dd1e1bf3ebb52cdb877fb359e8978a51576e3, 1cfef80d4c2b2c599189f36f36320b205d9447d9 < eae0aec245712c52a3ce9c05575b541a9eef5282, 1cfef80d4c2b2c599189f36f36320b205d9447d9 < 8a2e4d37afb8500b276e5ee903dee06f50ab0494, c33d5a5c5b2c79326190885040f1643793c67b29, 29d6fe395087710280f8e11d4ae79569c4cb14b7, 5.15.126 < 5.15.159, 6.1.45 < 6.1.91, 5.10.190 < 5.11, 6.4.10 < 6.5, 6.5
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 30 May 2024 · Last source change 5 Aug 2026, 11:32 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-36278
Product sourceCNA
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-36278↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-36928 · cve.blacktree.nl