CVE Vulnerability Catalog

In the Linux kernel, the nvme-tcp driver's nvme_tcp_handle_r2t() does not check the direction of the request the R2T refers to. A malicious controller can send an R2T for a READ and the host will answer it, sending the READ destination buffer (containing stale kernel data) to the controller. This leaks host memory, including struct page pointers.

In the Linux kernel, the nvme-tcp driver's nvme_tcp_recv_data() completes a request once the current C2HData PDU is consumed, without comparing total bytes received against the length the command asked for. A malicious controller can answer a 4096-byte read with 512 bytes and have it reported as complete, exposing 3584 bytes of stale page data to user space. The fix counts received bytes and refuses to complete an incomplete read.

A use-after-free vulnerability exists in the Linux kernel's SCTP handling. A remote peer can bundle COOKIE ECHO, SHUTDOWN and SHUTDOWN ACK chunks in a single packet, causing the association and its transports to be freed, after which the endpoint loop writes to freed memory. This occurs when the packet is processed from the socket backlog in task context.

In the Linux kernel, sctp_rcv() resolves the transport once per packet and keeps it in chunk->transport until processing completes. An authenticated ASCONF DEL-IP can remove and free that transport via RCU in the meantime, and a subsequent delayed SACK then reads the freed transport's state. This results in a use-after-free.

The Linux kernel has a NULL pointer dereference vulnerability in the SCTP implementation when completing a stream reconfiguration request that has not yet been transmitted. When a request is already published in asoc->strreset_chunk but has no assigned transport (chunk->transport == NULL), stopping the reconf timer dereferences NULL and panics the kernel. It can be triggered locally by an unprivileged process or remotely via a crafted RECONF packet.

In the Linux kernel, a cached SCTP RECONF chunk may contain more than one request parameter. A duplicate response can process the same ADD_OUT request again, rolling back the outcnt counter twice and potentially underflowing it. The fix tracks outstanding request types as bits and ignores later responses.

In the Linux kernel, in the power: supply: bq24257 driver the STAT-pin interrupt is devm-managed and stays armed until devm cleanup after remove() returns. remove() cancels bq->iilimit_setup_work while the threaded handler can still fire and reschedule it, dereferencing freed memory. The fix uses devm_delayed_work_autocancel() and registers the work before the interrupt request.

In the Linux kernel, in the power: supply: bq256xx driver the USB-PHY notifier queues usb_work, whose handler calls power_supply_changed(bq->charger). The reset devm action is registered before the power supplies, so devm frees bq->charger before the action runs, and a still-queued usb_work can dereference it. The fix registers the reset action after the supplies and initializes usb_work before the notifiers.

In the Linux kernel, in the power: supply: bq25890 driver bq25890_fw_probe() acquires a reference to a secondary charger via power_supply_get_by_name(), but does not release it on later probe failures or on driver detach. The fix registers a device-managed cleanup action immediately after acquiring the reference.

In the Linux kernel, the charger-manager (power: supply) driver has a use-after-free vulnerability. Regulators are freed (regulator_put) before sysfs entries are unregistered (power_supply_unregister), and sysfs entries are registered before regulators are acquired, allowing a race condition and access to freed handles.

In the Linux kernel, in the power: supply: cros_usbpd-charger driver cros_usbpd_charger_probe() reads two port counts from the EC and uses num_charger_ports as the loop bound when populating the fixed-size ports[] array of 8 entries. Without validation against EC_USB_PD_MAX_PORTS, a malfunctioning or malicious EC can report up to 255, causing a slab out-of-bounds write. The fix rejects a port count larger than the array can hold.

In the Linux kernel, in the power: supply: cros_usbpd-charger driver the probe iterates based on the raw charger port count returned by the embedded controller. The only check is against the number of USB PD ports also defined by the EC, so a malicious EC could return an inaccurate count (up to 255), causing an out-of-bounds write and memory corruption. The fix limits port counts to EC_USB_PD_MAX_PORTS.

In the Linux kernel, in the power: supply: lp8727 driver lp8727_release_irq() cancels pchg->work before freeing the IRQ, so an IRQ delivered in between can re-arm the work through the threaded handler. After .remove returns, the devm layer frees pchg while lp8727_delayed_func() may still run and dereference it. The fix frees the IRQ first, then cancels the work.

In the Linux kernel, the lp8788-charger driver has a use-after-free on device removal. lp8788_charger_remove() flushes charger_work before unregistering IRQs, so an IRQ thread can queue work after flush_work() returns, and the work then dereferences freed pchg memory.

In the Linux kernel, the qcom_battmgr driver has a use-after-free. qcom_battmgr_pdr_notify() queues enable_work when the PMIC GLINK service comes up, and the PMIC GLINK client stays on the client list until devres release, allowing PDR notifications to keep queueing work that accesses freed battmgr memory.

In the Linux kernel, the qcom_battmgr driver's qcom_battmgr_sc8280xp_strcpy() copies firmware strings without guaranteeing a terminator when the firmware does not use Pascal-style strings. Fields model_number, serial_number, and oem_info may lack a null terminator, causing out-of-bounds reads when printed to userspace.

In the Linux kernel, the rt9455 power supply driver contains a use-after-free bug. During driver removal (rt9455_remove), delayed works are cancelled in the wrong order — batt_presence_work can queue max_charging_time_work after it has been cancelled, causing a dereference of the freed rt9455_info structure. The issue also occurs in the probe error path when rt9455_hw_init() fails after the IRQ has been requested.

In the Linux kernel, the twl4030_charger driver has a use-after-free. twl4030_bci_remove() does not cancel two workers (bci->work and bci->current_worker) that dereference the devm-allocated bci structure, potentially accessing freed memory after device removal.

In the Linux kernel, the ucs1002 driver has a use-after-free on removal. The driver has no remove callback, so unbind runs through devm, but devm frees the alert IRQ without cancelling the health_poll delayed work, which can then run after driver data is freed.

In the Linux kernel, the max17040 driver's max17040_get_vcell() and max17040_get_soc() ignore errors from regmap_read(). When an I2C transfer fails, the uninitialized register value is converted and reported to userspace as valid voltage or state of charge, and the polling worker can replace the cached state with a bogus value.