PULSE
FEED
ransomwhitearmor reclama a Gamdom · Otherransomfalcon reclama a Beasley Allen Law Firm · US · Professional Servicesransomqilin reclama a RaceTrakka · AU · Retail & E-Commerceransomqilin reclama a Smith Feddeler & Smith · US · Professional Servicesransomqilin reclama a Delta Electric Power Association · US · Energy & Utilitiesransomqilin reclama a Bangor Wholesale Laminates · GB · Manufacturingransomqilin reclama a TeleTronic · ES · Technologyransomqilin reclama a FIRMENGRUPPE APPL Holding GmbH · DE · Otherransomqilin reclama a Premier Medical Group · US · Healthcareransomqilin reclama a Zachary Confections · US · Retail & E-Commerceransomqilin reclama a THOMAS JORDAN, P.A · US · Professional Servicesransomqilin reclama a Five Star Sheets · US · Retail & E-Commerceransomqilin reclama a Power Funding · GB · Financial Servicesransomqilin reclama a Mountain Rheumatology · US · Healthcareransomwhitearmor reclama a Gamdom · Otherransomfalcon reclama a Beasley Allen Law Firm · US · Professional Servicesransomqilin reclama a RaceTrakka · AU · Retail & E-Commerceransomqilin reclama a Smith Feddeler & Smith · US · Professional Servicesransomqilin reclama a Delta Electric Power Association · US · Energy & Utilitiesransomqilin reclama a Bangor Wholesale Laminates · GB · Manufacturingransomqilin reclama a TeleTronic · ES · Technologyransomqilin reclama a FIRMENGRUPPE APPL Holding GmbH · DE · Otherransomqilin reclama a Premier Medical Group · US · Healthcareransomqilin reclama a Zachary Confections · US · Retail & E-Commerceransomqilin reclama a THOMAS JORDAN, P.A · US · Professional Servicesransomqilin reclama a Five Star Sheets · US · Retail & E-Commerceransomqilin reclama a Power Funding · GB · Financial Servicesransomqilin reclama a Mountain Rheumatology · US · Healthcare
← All CVEs
CVE WatchOct 15, 2026

CVE-2026-31546

In the Linux kernel, the following vulnerability has been resolved: net: bonding: fix NULL deref in bond_debug_rlb_hash_show rlb_clear_sla

CVSS

5.5

Medium

EPSS

0.1%

p2

KEV

—

Exploit Today

1

0-100

Published: Apr 24, 2026 · Last modified: Oct 15, 2026 · CWE-476

EPSS · 30d
0.1%EPSS · 30 days0.2%
2026-09-272026-10-25
Technical description

In the Linux kernel, the following vulnerability has been resolved: net: bonding: fix NULL deref in bond_debug_rlb_hash_show rlb_clear_slave intentionally keeps RLB hash-table entries on the rx_hashtbl_used_head list with slave set to NULL when no replacement slave is available. However, bond_debug_rlb_hash_show visites client_info->slave without checking if it's NULL. Other used-list iterators in bond_alb.c already handle this NULL-slave state safely: - rlb_update_client returns early on !client_info->slave - rlb_req_update_slave_clients, rlb_clear_slave, and rlb_rebalance compare slave values before visiting - lb_req_update_subnet_clients continues if slave is NULL The following NULL deref crash can be trigger in bond_debug_rlb_hash_show: [ 1.289791] BUG: kernel NULL pointer dereference, address: 0000000000000000 [ 1.292058] RIP: 0010:bond_debug_rlb_hash_show (drivers/net/bonding/bond_debugfs.c:41) [ 1.293101] RSP: 0018:ffffc900004a7d00 EFLAGS: 00010286 [ 1.293333] RAX: 0000000000000000 RBX: ffff888102b48200 RCX: ffff888102b48204 [ 1.293631] RDX: ffff888102b48200 RSI: ffffffff839daad5 RDI: ffff888102815078 [ 1.293924] RBP: ffff888102815078 R08: ffff888102b4820e R09: 0000000000000000 [ 1.294267] R10: 0000000000000000 R11: 0000000000000000 R12: ffff888100f929c0 [ 1.294564] R13: ffff888100f92a00 R14: 0000000000000001 R15: ffffc900004a7ed8 [ 1.294864] FS: 0000000001395380(0000) GS:ffff888196e75000(0000) knlGS:0000000000000000 [ 1.295239] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1.295480] CR2: 0000000000000000 CR3: 0000000102adc004 CR4: 0000000000772ef0 [ 1.295897] Call Trace: [ 1.296134] seq_read_iter (fs/seq_file.c:231) [ 1.296341] seq_read (fs/seq_file.c:164) [ 1.296493] full_proxy_read (fs/debugfs/file.c:378 (discriminator 1)) [ 1.296658] vfs_read (fs/read_write.c:572) [ 1.296981] ksys_read (fs/read_write.c:717) [ 1.297132] do_syscall_64 (arch/x86/entry/syscall_64.c:63 (discriminator 1) arch/x86/entry/syscall_64.c:94 (discriminator 1)) [ 1.297325] entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) Add a NULL check and print "(none)" for entries with no assigned slave.

Official references
Related CVEs
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-823896.5 MED
—
———In the Bluetooth Classic Hands-Free Profile Audio Gateway role, hfp_ag_create() in subsys/bluetooth/host/classic/hfp_ag.c starts an SDP discovery toward the peer, which links the embedded ag->sdp_param._node into the SDP client's pending request list in subsys/bluetooth/host/classic/sdp.c. If the subsequent bt_rfcomm_dlc_connect() call fails, bt_hfp_ag_connect() cleaned up by memset()-ing the entire AG object while that node was still linked, and while ag->slc_work could still be queued on the system work queue. An in-flight SDP discovery cannot be cancelled — bt_sdp_discover_cancel() is declared in the public header but has no implementation — so the request stays in the list with its func, pool and uuid pointers zeroed. The RFCOMM channel passed to bt_hfp_ag_connect() is taken from the peer's own SDP Hands-Free service record in the normal AG flow (bt_sdp_get_proto_param() performs no range validation, and samples/bluetooth/classic/handsfree_ag feeds the value straight through), so a remote BR/EDR device in radio range that advertises an RFCOMM channel outside the valid range 0x01..0x1e deterministically forces bt_rfcomm_dlc_connect() to fail and reach the wipe. Reading the peer's SDP record requires no pairing, and the peer can also trigger the failure by dropping the ACL or racing an RFCOMM DLC on the same DLCI at the right moment. When the SDP client next advances its request list, sdp_client_discover() dereferences the zeroed parameters — net_buf_alloc(param->pool, …) with a NULL pool and param->uuid->type — and the result-notification paths call through the NULL params->func. Zeroing a linked node also truncates the request list behind a stale tail pointer, and re-arming the freed AG slot re-appends the same node and can produce a self-looping list that hangs the Bluetooth RX thread. The impact is a crash or hang of the Bluetooth stack; the written value is a constant zero at a fixed static address, so no attacker-controlled write is available. Only builds with CONFIG_BT_CLASSIC and CONFIG_BT_HFP_AG that use the Audio Gateway role are affected.6h
CVE-2026-1164975.5 MED
—
———A NULL pointer dereference vulnerability was found in gssproxy. When a GSSX_INIT_SEC_CONTEXT request is received with the target_name field absent, the daemon dereferences the resulting NULL pointer and crashes. The request requires no authentication, allowing any local user to crash the gssproxy daemon via its Unix socket. The daemon does not automatically restart, resulting in a persistent denial of service that also affects dependent services such as Kerberized NFS and IdM.6h
CVE-2026-96432—
—
———A malicious or compromised HTTP/2 server withholding SETTINGS ACK can send RST_STREAM on a completed stream, planting a null pointer, and then send a PUSH_PROMISE for that stream, causing a null pointer dereference in the QNetworkAccessManager class of the Qt Network module that crashes the application.8h
CVE-2026-829466.5 MED
—
——0SOEM version 2.0.0 and earlier contains a vulnerability where a malicious device can crash the master system. When the software receives an error response, it clears an internal pointer but continues processing. If another message arrives before timeout, the software attempts to use the cleared pointer, causing a crash. An attacker can trigger this with a simple sequence of two messages.8h
CVE-2026-1161473.7 LOW
—
——0ImageMagick before 6.9.13-58 and 7.x before 7.1.2-33 contains a null pointer dereference in the DJVU decoder because the result of a memory allocation is not checked before use. Attackers can supply a DJVU image that, when processed under conditions where the allocation fails, crashes the process and causes a denial of service.6h
CVE-2026-1104917.5 HIG
44.2%
——13The ONVIF service on the E3 can be rendered unresponsive by sending malformed or incomplete requests to certain operations. The affected service stops accepting new connections while the rest of the device continues operating normally, and will recover automatically after a period. This can be triggered repeatedly by any unauthenticated party with network access to the device.3d