Linux
Monthly
The mt7925 WiFi driver (mt76 subsystem) in the Linux kernel fails to cancel a deferred work item on the device stop path, creating a 5-second race window during multi-link operation (MLO) power-save setup. If the mt7925 PCIe or USB device is torn down within that window, the surviving timer fires against a workqueue that has already been destroyed, triggering a kernel WARNING and potential crash. No public exploit has been identified; EPSS is 0.17% (6th percentile), and the bug requires local access to hardware running an affected kernel with MLO power-save active.
Out-of-bounds write in the Linux kernel mt76/mt7996 WiFi driver allows a malicious or malfunctioning MediaTek mt7996 chip to corrupt kernel heap memory. The vulnerability exists in mt7996_mcu_get_eeprom(), which derives a destination offset into dev->mt76.eeprom.data from a device-controlled field (event->addr, a __le32 in the MCU response) without bounding that offset before performing the EFUSE/EXT block copy. A compromised or deliberately crafted mt7996 device can trigger an OOB write of up to MT7996_EXT_EEPROM_BLOCK_SIZE bytes into kernel memory, with potential for privilege escalation or denial of service. No public exploit is identified at time of analysis and EPSS is 0.15%, consistent with the narrow attack surface requiring hardware-level adversarial control.
Out-of-bounds memory read in the Linux kernel mt76/mt7996 Wi-Fi driver allows a local attacker with ability to supply a truncated EEPROM firmware file to trigger kernel memory disclosure or crash during driver initialization. The driver unconditionally copies and validates the default EEPROM firmware without first checking its length against the expected MT7996_EEPROM_SIZE constant, so a file shorter than that threshold causes reads past the end of the allocated firmware buffer. No public exploit has been identified at time of analysis; EPSS sits at 0.17% (6th percentile), reflecting the hardware-gated, local-access constraint.
Slab-use-after-free in the Linux kernel vsock/virtio transport driver allows a local attacker to trigger kernel memory corruption by exploiting a work-item flush ordering bug during device removal. The virtio_vsock_remove() path flushes work items without respecting producer-to-consumer dependencies (tx_work → send_pkt_work → rx_work), allowing kfree(vsock) to race with a newly queued rx_work item, as confirmed by KASAN reporting a UAF read in virtio_transport_rx_work. No public exploit exists and no active exploitation has been identified; EPSS is 0.17% (6th percentile). Patches are available in stable releases 6.12.109, 6.18.50, 7.2.4, and 7.3-rc1.
Out-of-bounds kernel heap write in the Linux kernel's DS28E17 1-Wire-to-I2C bridge driver allows a local attacker controlling a malicious I2C slave device to write up to 222 bytes past a 34-byte kernel buffer. The driver's w1_f19_i2c_read() unconditionally trusts a device-supplied length byte (0-255) on I2C_M_RECV_LEN transactions, but the caller buffer is only I2C_SMBUS_BLOCK_MAX + 2 bytes; the SMBus core's own BLOCK_MAX check runs only after the overwrite has already occurred. No public exploit has been identified at time of analysis; EPSS sits at 0.17%, reflecting the niche hardware prerequisite.
Improper sysctl table placement in the Linux kernel allows a local low-privileged user to modify the global `cad_pid` setting - which controls which process receives the Ctrl-Alt-Delete console signal - by abusing unprivileged user and PID namespace creation. A non-root user can call `unshare(CLONE_NEWUSER|CLONE_NEWPID)` to gain apparent root privileges in a child namespace and then overwrite the globally-scoped `/proc/sys/kernel/cad_pid`, even though `kill_cad_pid()` operates exclusively in the root namespace. No public exploit is identified at time of analysis; EPSS stands at 0.20% (10th percentile), and no CISA KEV listing exists.
Use-after-free in the Linux kernel's Smack LSM `smack_file_send_sigiotask()` function allows a local attacker with low privileges to trigger kernel memory corruption by racing credential pointer changes on a non-current task. The function incorrectly accessed both `tsk->cred` (subjective credentials, unprotected) and `__task_cred(tsk)` (objective credentials) on the same task; because a task may change its own `->cred` pointer at any time without synchronization, the first access can race with a credential transition, yielding a freed `struct cred` deref. The author confirmed KASAN-reported UAF reproduction and verified the fix. No public exploit exists and EPSS is low at 0.17%, but the CVSS-assessed local impact (C:H/I:H/A:H) reflects the potential for privilege escalation on affected kernels.
Use-after-free in the Linux kernel's ksmbd in-kernel SMB3 server lets any authenticated SMB client holding a durable batch oplock corrupt kernel memory during oplock-break notification. smb2_oplock_break_noti() reads opinfo->conn without a lock and dereferences it after two sleep-capable allocations; if the durable handle owning the oplock is disconnected concurrently, the connection is freed and a racing break from another connection resurrects the stale pointer, leading to a use-after-free in ksmbd_conn_write(). No public exploit identified at time of analysis, and EPSS is low (0.17%), consistent with a race-dependent, DoS-leaning memory-safety bug rather than a turnkey RCE.
The krb5 crypto subsystem in the Linux kernel fails to zero derived Kerberos key material before freeing memory buffers, leaving sensitive cryptographic keys resident in freed slab allocator objects. Both `crypto_krb5_prepare_encryption()` and `crypto_krb5_prepare_checksum()` call plain `kfree()` instead of the security-aware `kfree_sensitive()` wrapper, which would first zero the allocation. Systems using Kerberos-authenticated kernel services - primarily NFSv4 with sec=krb5 or CIFS/SMB with Kerberos - on kernel versions from commit 3936f02b through the stable fixes are affected; no public exploit or active exploitation has been identified.
Unauthorized cryptographic hardware access in KVM for s390 (IBM Z) nested virtualization allows a low-privileged nested guest to access AP queues (hardware crypto devices) that were explicitly revoked from its allocation. When the KVM VSIE subsystem shadows a format0 APCB (Adjunct Processor Control Block) from a crycb type 0 or 1 structure, it only copies bits 0-63 but leaves bits 64-255 unchanged from whatever stale state existed in the vsie shadow page. A nested (L2) guest exploiting this retains access to cryptographic devices beyond those granted by the host hypervisor, potentially exposing cryptographic keys and operations belonging to other workloads. No public exploit has been identified at time of analysis and no CISA KEV listing exists.
Use-after-free in the Linux kernel Bluetooth ISO stack allows an adjacent unauthenticated attacker to corrupt kernel memory and potentially execute arbitrary code. The flaw is a race condition in iso_conn_ready(): when a BIS listener socket is concurrently closed while an incoming Bluetooth Isochronous connection is being processed, a child socket is allocated that holds a dangling pointer to the now-freed parent socket, which is later dereferenced during disconnect via iso_chan_del() and bt_accept_unlink(). Patches are available across multiple stable kernel branches (6.12.109, 7.2.4, 6.18.50, and 7.3-rc1); no public exploit code or active exploitation has been identified at time of analysis.
Incorrect permission assignment on a critical resource in Pardus LightDM Greeter allows a local low-privileged user to read sensitive authentication material or tamper with greeter configuration, achieving high confidentiality and integrity impact without elevated rights. All versions before 0.4.15 of the greeter - a graphical login component shipped with Pardus, the Turkish government-backed Linux distribution maintained by TÜBİTAK BİLGEM - are affected. No public exploit or active exploitation has been identified; a vendor-released patch is available. No special configuration is required beyond having a local user account on an affected system.
Out-of-bounds buffer access in the Linux kernel's synaptics-rmi4 driver exposes systems with Synaptics RMI4 touchpad hardware to kernel memory corruption triggered by a copy-paste typo in F55 electrode initialization. On affected hardware where the receiver (RX) electrode count exceeds the transmitter (TX) count, the incorrectly propagated TX value causes F54 diagnostic routines to calculate an inflated report buffer size, enabling potential OOB reads or writes in kernel space. Patched stable releases are available across all maintained kernel branches; no public exploit code or active exploitation (CISA KEV) has been identified, and EPSS remains at 0.21%.
Race condition in the Linux kernel's ovpn (kernel-native OpenVPN) module allows a workqueue callback to continue executing within module text after that text has been freed during module teardown, creating a use-after-free condition in kernel space. The flaw exists because ovpn queues work items on the global system workqueue rather than a module-owned queue, leaving no driver-controlled drain point to guarantee all callbacks have exited before the module's code segment is released. Systems actively using the kernel-native ovpn module are at risk of kernel memory corruption or crash during module unload; no public exploit has been identified at time of analysis and EPSS is 0.20%.
NULL pointer dereference in the Linux kernel's psxpad-spi driver crashes the kernel when system suspend is triggered on hardware using SPI-connected PlayStation controllers. The probe() function in drivers/input/joystick/psxpad-spi.c omits the spi_set_drvdata() call that stores per-device state, so psxpad_spi_suspend() unconditionally dereferences a NULL pointer on suspend entry, causing a kernel panic. Patches are available across all active stable kernel branches (5.10 through 7.2); EPSS is 0.21% and no active exploitation has been identified.
Uninitialized pointer dereference in the Linux kernel's MediaTek GPU power-domain driver (`pmdomain/mediatek/mfg`) can trigger a kernel fault or incorrect OPP (Operating Performance Point) configuration on first device attachment. The `prev_o` variable in `mtk_mfg_attach_dev()` is read in a conditional branch on the first loop iteration before ever being assigned, meaning it holds an indeterminate stack value; if that value is non-NULL, the kernel dereferences a stale or garbage pointer. Affected versions span stable kernel trees from commit f08e7a4e8d6a through the fixed points in 7.1.10, 7.2, and 6.19. No public exploit code and no CISA KEV listing are present; EPSS at 0.19% (9th percentile) reflects minimal real-world exploitation interest.
Use-after-free in the Linux kernel's MediaTek power domain driver exposes kernel memory to potential corruption via a dangling device-tree node pointer. In scpsys_get_bus_protection_legacy(), two error paths call of_node_put() to release infracfg and SMI device-tree node references before those nodes are passed to dev_err_probe() with the %pOF format specifier; if the put drops the last reference, the formatter dereferences freed memory. Vendor patches are available for Linux 6.18.46, 7.1.10, and 7.2, and EPSS exploitation probability sits at 0.20% (10th percentile) with no confirmed active exploitation.
Out-of-bounds memory read in the Linux kernel's DRM HDMI connector subsystem allows a local, low-privileged user to potentially leak up to 32 bytes of adjacent kernel heap memory or trigger a page fault leading to kernel crash. The flaw exists in a helper function that copies audio infoframe data using the destination buffer size (60 bytes) rather than the source structure size (28 bytes), reading 32 bytes beyond the source allocation. No public exploit code exists, and EPSS sits at the 10th percentile; however, the availability impact is real - the overread can cross a page boundary and cause an access violation.
Out-of-bounds memory access in the Linux kernel's Loongson2 MMC driver allows a local authenticated user to corrupt kernel memory through incorrect scatterlist indexing in the mmc: loongson2 subsystem. The functions `ls2k0500_mmc_reorder_cmd_data()` and `ls2k2000_mmc_reorder_cmd_data()` use `for_each_sg()` to iterate a scatterlist but then incorrectly re-index the current `sg` pointer as if it were an array base (using `&sg[i]`), causing access to wrong or out-of-bounds scatterlist entries. This memory corruption can lead to full kernel compromise - confidentiality, integrity, and availability loss - on systems using Loongson LS2K0500 or LS2K2000 SoCs equipped with MMC storage. No public exploit has been identified at time of analysis.
Out-of-bounds memory reads in the Linux kernel's drm/amdkfd CRAT table parser allow a local attacker to leak kernel memory and potentially crash the system on AMD GPU/APU-equipped hosts. The CRAT (Component Resource Affinity Table) subtype parser validates that a subtype header fits within the image buffer but fails to verify that the advertised subtype length field also stays within bounds, enabling kfd_parse_subtype() to cast the header pointer beyond valid memory when a malformed CRAT table is supplied. No public exploit has been identified at time of analysis; EPSS is 0.19%, placing this in the 9th percentile.
Out-of-bounds table access in the Linux kernel fp9931 regulator driver exposes kernel memory to corruption via a malformed VPOS/VNEG voltage selector lookup table. The fp9931 driver's VPOSNEG_table[] contains two defects: a duplicate 7.04V entry that shifts all subsequent selector mappings by one, and a truncated table of only 41 entries instead of the required 64, meaning any selector value above 0x28 triggers an out-of-bounds access in kernel memory. Devices incorporating the FP9931 PMIC (a display-panel power regulator) running affected kernel versions are vulnerable; exploitation probability is very low (EPSS 0.20%, 10th percentile) with no public exploit and no confirmed active exploitation.
Out-of-bounds kernel memory read in the Linux kernel DRM log subsystem allows a local low-privileged user to potentially disclose kernel memory contents or crash the system. The flaw resides in drm_log_draw_kmsg_record(), where an unsigned integer underflow on a zero-length message causes an array access at offset UINT_MAX (0xFFFFFFFF) rather than a valid buffer position. No public exploit exists and EPSS sits at 0.20% (10th percentile), indicating low observed exploitation interest, though the kernel DRM panic-display path is reachable on any system with a GPU using the DRM framework.
Type-confusion memory access in the Linux kernel BPF subsystem allows a local attacker with BPF-capable privileges to read or corrupt kernel memory via the bpf_tcp_gen_syncookie and bpf_tcp_check_syncookie helpers. Both helpers accept a generic sock_common pointer (ARG_PTR_TO_BTF_ID_SOCK_COMMON) but dereference fullsock-specific fields without first confirming the socket is in TCP_LISTEN state, meaning a mini-socket passed to either helper causes an out-of-bounds struct field access. No public exploit has been identified and EPSS sits at 0.20% (10th percentile), though the C:H/I:H CVSS impact signals the potential to compromise kernel memory integrity if exercised by a sufficiently privileged local process.
Use-after-free and race condition in the Linux kernel's amba-pl011 ARM UART serial driver during DMA teardown allows a local attacker to corrupt kernel memory, potentially gaining arbitrary code execution or causing a denial of service. The flaw exists because dmaengine_terminate_all() returns without waiting for in-flight callbacks to complete, enabling the TX DMA callback to dereference already-freed TX buffer memory; a parallel race exists in the RX path where the poll timer accesses RX buffers without holding the port lock. Patches are available across multiple stable kernel branches; no public exploit code or active exploitation (KEV) has been identified at time of analysis.
Out-of-bounds array access in the Linux kernel's Thunderbolt driver exposes local low-privileged users to potential kernel memory corruption and privilege escalation. The flaw in tb_consumed_dp_bandwidth() sizes the group_reserved[] array at MAX_GROUPS entries (indices 0 through MAX_GROUPS-1) but uses Group IDs directly as indices, where valid IDs run from 1 through MAX_GROUPS - causing an off-by-one that reads and writes one element past the array boundary when the highest bandwidth group is processed. Patches are available across multiple stable kernel branches (6.12.x, 6.18.x, 7.1.x, 7.2), and no public exploit code has been identified at time of analysis.
Out-of-bounds kernel memory reads in the Linux kernel's ovpn (in-kernel OpenVPN) driver allow a local attacker with low privileges to leak kernel memory by abusing a missing ownership check on the sk_user_data socket field. The driver dereferences sk_user_data as an ovpn-internal structure without first confirming that encap_type identifies the socket as ovpn-owned, so when BPF SOCKMAP or another subsystem has populated sk_user_data with a different pointer type, ovpn misinterprets that memory and reads out of bounds. Affected kernels span 6.16 through pre-patch stable releases; no public exploit has been identified and EPSS sits at 0.21% (11th percentile), but kernel memory disclosure can seed further privilege escalation.
Btrfs in the Linux kernel fails to reinitialize inode address-space mapping flags and minimum folio order when re-reading previously evicted cached inodes, causing a kernel assertion failure and system crash (denial of service). The defect surfaces only when btrfs is mounted with a block size larger than the host memory page size - a non-default but valid configuration - and manifests after a create/evict/re-read inode cycle. No public exploit code exists and EPSS is 0.20% (10th percentile), reflecting negligible real-world exploitation probability beyond accidental triggering.
Use-after-free in the Linux kernel's pata_sl82c105 PATA bridge driver allows a local low-privileged user to potentially achieve kernel memory corruption leading to privilege escalation on systems equipped with the SL82C105 PCI bridge chip. The defect was introduced by commit 44c10138fd4b, which replaced a PCI configuration-space read with direct access to the cached revision field of a PCI device struct - but left that access after the reference was dropped via pci_dev_put(), creating a window where the bridge struct may be freed before the read occurs. Patches have been backported across multiple long-term stable kernel branches; no public exploit code or active exploitation has been identified at time of analysis.
Out-of-bounds write in the Linux kernel's `dev_validate_header()` network function allows a local process holding `CAP_SYS_RAWIO` to corrupt kernel memory by sending a raw packet with a short link-layer header while the target network device is concurrently reconfigured to increase `hard_header_len`. The `memset` zero-padding operation writes past the skb headroom reserved at allocation time, producing a silent memory corruption that is worse than the pre-existing `skb_under_panic()` it masks. Patches are available across multiple stable kernel branches; EPSS stands at 0.24% with no public exploit or CISA KEV listing.
Local privilege escalation / host memory corruption in the Linux kernel's KVM x86 shadow-MMU allows a malicious or buggy guest to trigger a slab use-after-free on the KVM host. When KVM derives a child shadow page's role from an invalid/obsolete parent root, it fails to clear role.invalid, violating the invariant that invalid pages stay off the active MMU list; __kvm_mmu_prepare_zap_page() then uses list_add() instead of list_move(), corrupting the list and freeing a shadow page that is still referenced, producing a KASAN slab-use-after-free in __kvm_mmu_get_shadow_page. There is no public exploit identified at time of analysis and EPSS is low (0.21%), but the fix is a hardening/defense-in-depth patch that also adds a WARN when an invalid parent is encountered.
Out-of-bounds kernel heap write in the Linux kernel's GRO (Generic Receive Offload) BIG TCP path allows corruption of memory before skb->head when aggregating oversized (>64KB) packets. The flaw stems from skb_gro_receive() using a loose headroom check introduced by the IPv4 BIG TCP support commit (b1a78b9b9886); crafted frames - for example injected via AF_PACKET with a MAC header under 8 bytes - pass validation, so ipv6_gro_complete()'s memmove() for the temporary HBH jumbo header writes before skb->head and wraps skb->mac_header. It also let software VLAN and encapsulated flows (SIT/IPv6-in-IPv4) aggregate beyond 64KB. No public exploit is identified at time of analysis and EPSS is low (0.19%), and the issue affects only older stable branches (e.g. 6.18.y), not mainline 7.0+.
Boot registry parameter injection in IGEL OS 12 (before 12.7.6) and IGEL OS 11 (before 11.11.150) allows an attacker with physical access to execute arbitrary Linux kernel command-line parameters by writing to an unencrypted, unsigned configuration partition that the signed bootloader reads at startup. The attack is particularly dangerous because it does not alter the measured boot code path, meaning TPM PCR attestation does not detect the tampering - effectively defeating the trust assumptions of the secure boot and full-disk encryption stack. A publicly available exploit script and a DEF CON 34 presentation detail the technique; no CISA KEV listing has been issued at time of analysis, indicating exploitation has not been confirmed at scale.
vmclock in the Linux kernel exposes a shared ABI memory page that a low-privileged guest process can upgrade from read-only to writable using mprotect(), allowing direct corruption of host-maintained timekeeping fields including sequence counters, UTC time, and TSC offsets. Affected deployments are virtualized Linux guests running kernels prior to patched stable releases 6.18.47, 7.2.1, and 7.1.11, where the vmclock miscdevice driver fails to clear VM_MAYWRITE on read-only mmap paths. No public exploit code has been identified at time of analysis, and EPSS at 0.15% (5th percentile) reflects low observed exploitation pressure despite a CVSS 8.8 score driven by the scope-changing guest-to-host integrity impact.
Out-of-bounds memory write in the Linux kernel's device tree reserved memory subsystem allows an attacker with control over device tree content to corrupt kernel memory at boot time, with theoretical full kernel compromise (C:H/I:H/A:H). The fdt_scan_reserved_mem() function writes past the end of a fixed-size local array when a device tree blob defines more dynamically-placed /reserved-memory subnodes than MAX_RESERVED_REGIONS allows. Despite a CVSS score of 8.4, exploitation is heavily constrained by the requirement to modify device tree content before boot - a capability requiring privileged firmware access - and EPSS at 0.16% (5th percentile) reflects negligible observed exploitation probability. No public exploit has been identified and the vulnerability is absent from CISA KEV.
Insufficient validation of S1G (802.11ah/Wi-Fi HaLow) Target Wake Time setup frames in the Linux kernel's mac80211 subsystem allows an unauthenticated adjacent-network attacker to submit a malformed individual TWT agreement whose parameter block is shorter than the full struct ieee80211_twt_params. The driver callback drv_add_twt_setup() and associated kernel tracepoint both consume the complete parameters structure regardless of the truncated length, potentially triggering kernel memory corruption, out-of-bounds reads exposing sensitive kernel memory, or a denial-of-service crash. No public exploit code has been identified, CISA KEV listing is absent, and patches are confirmed across seven stable kernel branches; real-world exposure is substantially narrowed by the requirement for S1G hardware.
Dangling pointer dereference in the Linux kernel Bluetooth ISO subsystem exposes systems running kernel versions prior to 6.18.44, 7.1.8, and 7.2 to potential kernel memory corruption from adjacent Bluetooth attackers. After iso_conn_del() is invoked, ISO sockets may continue to dereference the freed hcon (HCI connection) pointer due to imprecise reference-counting logic, creating a use-after-free-class condition in kernel space. Despite a high NVD CVSS score of 8.8, the EPSS rating of 0.15% (5th percentile) and absence from CISA KEV indicate no public exploit or observed active exploitation at time of analysis.
Deadlock in the Linux kernel's iomap subsystem allows local attackers to cause a denial of service by exhausting the shared bioset used by both iomap_split_ioend and its input bios. The circular dependency in bioset allocation halts I/O completion on iomap-backed filesystems (XFS, ext4 direct I/O) and can hang the affected system. No active exploitation has been confirmed (not in CISA KEV) and the EPSS probability is very low at 0.15% (5th percentile), but the impact on availability is total for the affected I/O path.
Bitmap overflow and incorrect global accounting in the Linux kernel's percpu-km memory allocator (`mm/percpu-km`) allow a local low-privileged attacker on SMP/NUMA systems to corrupt kernel memory, with potential for privilege escalation or kernel crash. Two separate commits introduced the flaws: a63d4ac4ab609 caused `pcpu_create_chunk()` to write beyond the `chunk->populated` bitmap when `nr_units > 1`, and b539b87fed37f introduced the companion `pcpu_nr_empty_pop_pages` accounting error. Fixes have been backported to eight stable kernel branches (5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103, 6.18.44, 7.1.8, 7.2); no public exploit has been identified at time of analysis.
Out-of-bounds read in the Linux kernel SCTP subsystem leaks up to four bytes of receive-buffer tail memory to remote unauthenticated attackers via a malformed INIT chunk. When an Adaptation Layer Indication parameter is sent with only its 4-byte header (omitting the mandatory 32-bit Adaptation Code Point), the kernel reads past the declared parameter boundary and copies those bytes into the state cookie of the INIT ACK response, exposing them to the peer. No public exploit has been identified and EPSS of 0.16% (6th percentile) indicates low exploitation probability, though the unauthenticated, network-accessible attack surface on any SCTP-enabled system warrants prompt patching.
Use-after-free in the Linux kernel ALSA PCM subsystem allows a local low-privilege attacker to corrupt kernel memory by exploiting a race between snd_pcm_drain() and snd_pcm_unlink() on linked streams. When a drain wait terminates by signal or timeout while group membership is concurrently modified by an unlink, a stack-allocated wait queue entry is left queued on a freed peer stream's sleep list; a subsequent wake_up() call then dereferences that freed stack frame. No public exploit code or CISA KEV listing exists at time of analysis; the EPSS of 0.16% (6th percentile) reflects low near-term exploitation probability.
Use-after-free in the Linux kernel's IPVS (IP Virtual Server) connection-synchronization path allows corruption of the connection hash table on backup directors running the IPVS sync daemon. When a synced connection is bound to a destination that carries the IP_VS_CONN_F_ONE_PACKET flag, expiry logic wrongly skips unlinking the conn_tab node, leaving a stale hash entry pointing at a freed struct ip_vs_conn. There is no public exploit identified at time of analysis and EPSS is very low (0.16%), so despite the auto-assigned 9.8 rating this is a memory-safety defect in a specialized load-balancing feature rather than a broadly weaponizable RCE.
Restriction bypass in the Linux kernel's io_uring subsystem allows a local low-privileged user to shed per-task io_uring security restrictions by executing exec(). When a task that has established io_uring restrictions calls exec(), the kernel's exec cancellation path invokes __io_uring_free(), which incorrectly frees both the task context and the per-task restriction simultaneously. Any io_uring ring created by the post-exec process is then entirely unrestricted, defeating sandbox and policy enforcement intended to constrain io_uring operations. No public exploit has been identified at time of analysis, but the CVSS score of 8.4 with Changed Scope (S:C) reflects that the bypass can expose confidentiality and integrity of resources guarded by the dropped restrictions.
The spi-qpic-snand NAND flash driver in Linux kernel 6.18 and later contains a command-ordering defect that causes every SET_FEATURE write to apply the previous operation's value rather than the intended one, producing an off-by-one effect. On Qualcomm IPQ5018-based hardware (confirmed on TP-Link Archer AX55 v1 with ESMT F50L1G41LB flash), this defect became destructive in v6.18 when SPI-NAND OTP support was introduced: the 'disable OTP mode' call erroneously leaves CFG_OTP_ENABLE set permanently, causing all subsequent flash reads to return OTP area content and all writes to fail with -EIO, rendering the device unbootable. No public exploit identified at time of analysis; EPSS of 0.15% (5th percentile) correctly reflects that this is a driver logic defect rather than a traditionally attacker-controllable vulnerability.
Integer truncation in the Linux kernel s390/dasd ECKD driver exposes IBM Z systems to a heap buffer overflow via a caller-controlled track range supplied to dasd_eckd_check_device_format(). The root cause is that fmt_buffer_size is declared as int while the buffer-size expression evaluates at size_t width, causing the result to be silently truncated on assignment; kzalloc() then allocates a buffer far smaller than needed, while the subsequent channel program builder operates on the untruncated track count and writes past the allocation. Systems running unpatched kernels before 6.6.151, 6.12.103, 6.18.44, 7.1.8, or 7.2 on s390 architecture face potential kernel heap corruption with consequences ranging from denial of service to local privilege escalation. No public exploit code exists and this vulnerability has not been added to the CISA KEV catalog at time of analysis.
Heap out-of-bounds memory access in the Linux kernel s390/zcrypt subsystem exposes EP11 crypto card administrative paths to local low-privileged users. The flaw resides in the domain value upper-limit check processed when sending EP11 CPRBs (Control Program Request Blocks) through custom zcrypt device nodes - the missing AP_DOMAINS (256) ceiling allows an attacker-supplied domain index to reach heap memory beyond the `perms->adm` structure. No public exploit code has been identified and this is not listed in CISA KEV, but the CVSS 7.8 local vector and confirmed multi-version patch backports across stable kernel branches indicate the Linux security team treats the impact as high. EPSS at 0.16% (6th percentile) reflects the platform-specific nature of the flaw.
Uninitialized receive buffer allocation in the Linux kernel's CAN J1939 transport layer exposes residual kernel heap memory to J1939 session participants. The function j1939_session_fresh_new() allocates a buffer without zeroing it, meaning any system running a CAN-capable Linux kernel with J1939 transport support may leak prior heap contents to peers exchanging Extended Transport Protocol (ETP) messages. No public exploit has been identified at time of analysis, and EPSS sits at 0.16% (6th percentile), consistent with a low-exploitation-probability kernel information-disclosure flaw in a specialized networking subsystem.
Out-of-bounds read and write vulnerabilities in the Linux kernel's softing CAN driver `fw_parse()` function allow a local low-privileged attacker to corrupt kernel DPRAM memory by supplying a crafted firmware image. Affected kernels span from 2.6.38 through pre-patch stable branches (5.10.x, 5.15.x, 6.1.x, 6.6.x, 6.12.x, 6.18.x, 7.1.x, and 7.2), with fixes backported across all active stable trees. No public exploit or active exploitation has been identified at time of analysis.
Memory corruption in the Linux kernel's VMware graphics (vmwgfx) DRM driver allows a local, low-privileged user on a VMware guest system to corrupt MOB (Memory Object Buffer) allocation metadata, leading to out-of-bounds reads or writes with high confidentiality, integrity, and availability impact. A field-naming bug in vmwgfx_resource.c writes boolean literals (0/false and 1/true) to the guest_memory_size unsigned-long field instead of the adjacent guest_memory_dirty bitfield, causing subsequent size-dependent operations to compute zero-length or wrap-around memory ranges on the MOB bitmap. No public exploit has been identified at time of analysis; EPSS is very low at 0.17% (6th percentile), though the CVSS 7.8 score reflects meaningful severity if triggered locally on a VMware guest.
Out-of-bounds memory corruption in the Linux kernel's vmwgfx DRM driver (vmw_external_bo_copy()) allows a local attacker with low-privilege DRM access to corrupt kernel memory via a crafted atomic display commit using an imported dma-buf framebuffer. Two distinct code paths are vulnerable: the equal-stride memcpy path suffers unsigned integer underflow when caller-supplied offsets exceed the buffer object size, and the non-equal-stride row-by-row path performs no bounds validation at all, allowing the copy loop to walk arbitrarily past the vmap end. Vendor-released patches are available across multiple stable kernel branches; no public exploit has been identified at time of analysis.
Out-of-bounds memory access in the Linux kernel's ltc4282 hwmon driver exposes systems with this hardware monitor to kernel memory disclosure or destabilization via the VGPIO minimum alarm voltage sysfs read path. A missing return statement in the driver causes the kernel to access memory beyond intended bounds when a local user reads the VGPIO channel's minimum alarm voltage attribute. Patch versions are available across multiple stable branches; no public exploit exists and EPSS sits at 0.17% (6th percentile), indicating very low current exploitation pressure despite the 7.8 CVSS score.
Denial of service in the Linux kernel's MediaTek mtk_eth_soc Ethernet driver: mtk_poll_controller() passed a net_device pointer to mtk_handle_irq_rx(), which expects a struct mtk_eth pointer (the value registered as the request_irq cookie). When CONFIG_NET_POLL_CONTROLLER is enabled and the ndo_poll_controller path is exercised (e.g. via netconsole/netpoll), the resulting bad-pointer dereference crashes the kernel. Only devices using the MediaTek SoC Ethernet driver are affected; there is no public exploit identified at time of analysis and EPSS is low (0.17%, 6th percentile).
Out-of-bounds slab write in the Linux kernel idpf network driver lets a malicious or compromised control plane (a PF or a hypervisor's device model) corrupt kernel heap memory during interrupt-vector setup. idpf_get_reg_intr_vecs() fills the reg_vals[] array bounded only by per-chunk num_vectors from a VIRTCHNL2_OP_ALLOC_VECTORS reply, which is never reconciled against the smaller num_allocated_vectors used to size the allocation, so a reply whose chunk counts sum higher writes struct idpf_vec_regs entries past the buffer. It carries a CVSS of 9.3, but EPSS is only 0.15%, it is not on CISA KEV, and there is no public exploit identified at time of analysis.
Use-after-free in the Linux kernel Bluetooth HCI sync subsystem exposes systems running vulnerable kernel versions (6.6.51-pre-6.7 and 6.8.9-pre-6.9) to potential kernel-context memory corruption from an adjacent attacker with no privileges required. The race condition occurs when hci_connect_acl/le_sync() callbacks dereference a freed hci_conn object during concurrent connection teardown, yielding a theoretical path to arbitrary code execution or kernel panic. No public exploit code has been identified at time of analysis, and EPSS at 0.15% (5th percentile) indicates very low observed exploitation activity.
Null pointer dereference in the Linux kernel's SCSI target iblock driver crashes the kernel when processing Persistent Reservation PREEMPT or RELEASE operations against storage backends with unimplemented PR hooks. Systems running the kernel as an iSCSI target are vulnerable - an attacker who can issue SCSI Persistent Reservation commands can trigger a kernel panic, causing a complete denial of service. No public exploit has been identified and EPSS sits at 0.17% (6th percentile), but patches are available across multiple stable branches and should be applied promptly on iSCSI target infrastructure.
Out-of-bounds vmemmap read in the Linux kernel's mm/util snapshot_page() crashes or leaks kernel memory during page isolation on memory-remove paths. The function incorrectly reads __page_2 when nr_pages > 1 rather than the correct threshold of nr_pages > 2, causing an illegal access into an adjacent, unmapped vmemmap section when an order-1 folio sits at a vmemmap section boundary. This was observed producing a kernel oops on ppc64le systems during DLPAR memory remove on a 22 TB LPAR. No public exploit is identified and EPSS is 0.17%, but the defect can cause a local denial-of-service or kernel memory disclosure. Patches are available across multiple stable kernel branches.
Denial-of-service in the Linux kernel's KVM subsystem on IBM Z (s390) mainframes stems from an unchecked airq_iv_create() return value in the zPCI adaptive-interrupt path. When AIBV allocation fails, zdev->aibv is left NULL and later dereferenced in kvm_zpci_set_airq(), crashing the host kernel. No public exploit identified at time of analysis and it is not in CISA KEV; EPSS is low at 0.17% (7th percentile), consistent with a hard-to-trigger, resource-exhaustion-dependent bug rather than a broadly weaponizable flaw.
Use-after-free in the Linux kernel Bluetooth SCO subsystem allows an adjacent unauthenticated attacker to corrupt freed kernel memory by exploiting a reference-counting race between socket close() and Bluetooth controller Disconnection Complete events. The race causes sco_conn_del() to perform a double put on a kref, confirmed by KASAN as slab-use-after-free, with potential to escalate privileges or crash the system. No public exploit or CISA KEV listing exists; EPSS is 0.17% (6th percentile), consistent with the race condition complexity limiting practical exploitation.
Incorrect unit conversion in the RISC-V memory management subsystem causes vmemmap_start_pfn to be computed with a physically misaligned base, violating the mask-alignment requirement for compound_info encoding in the sparse memory model. Linux kernel versions incorporating commit 476849b0fba4 on RISC-V hardware where DRAM base is not aligned to MAX_FOLIO_NR_PAGES × PAGE_SIZE are affected - a condition confirmed on QEMU virt machines and potentially other RISC-V platforms. CVSS 7.8 (AV:L/PR:L/C:H/I:H/A:H) reflects potential local privilege escalation via kernel memory corruption; EPSS of 0.17% (7th percentile) and no CISA KEV listing indicate no observed exploitation activity. No public exploit is identified at time of analysis.
Use-after-free in the Linux kernel's VXLAN transmit path (vxlan_xmit) lets a stale Ethernet header pointer be dereferenced after route_shortcircuit() calls pskb_may_pull() and reallocates skb->head, corrupting or reading freed memory when accessing eth->h_dest. The flaw affects systems using a VXLAN overlay interface and is most realistically a denial-of-service (kernel crash) with potential information disclosure; no public exploit identified at time of analysis and EPSS is low (0.18%). It is not listed in CISA KEV and no proof-of-concept is known.
Use-after-free in the Linux kernel's AMD MP2 I2C driver (i2c-amd-mp2) enables local low-privileged users to corrupt kernel memory, potentially achieving privilege escalation or system crash on AMD hardware. The flaw occurs during driver probe: when i2c_add_adapter() fails, devres frees the platform I2C context, but the MP2 PCI driver retains a stale pointer in its IRQ and system-sleep callback table, allowing subsequent dereference of freed memory. No public exploit exists and EPSS is 0.18% (7th percentile), reflecting the hardware-specific and error-path-dependent nature of this flaw; vendor-released patches are available across all major stable kernel branches.
Race condition and error-handling flaws in the i2c-imx I2C controller driver allow a NULL pointer dereference via the kernel interrupt handler on NXP i.MX SoC-based systems. The vulnerability affects multiple stable kernel branches (5.15 through 7.x) and is triggered when I2C slave registration fails partway through a PM runtime resume, leaving a stale or NULL pointer that the shared IRQ handler can dereference concurrently. The realistic impact is a kernel panic causing system unavailability; no public exploit exists and EPSS is 0.17%, consistent with no observed active exploitation.
Race condition in the Linux kernel's driver core `dev_has_sync_state()` exposes a TOCTOU (Time-of-Check Time-of-Use) flaw allowing local low-privileged users to potentially trigger kernel memory corruption, information disclosure, or a system crash. The function reads `dev->driver` twice without holding `device_lock()`, enabling a concurrent device unbind operation to clear the pointer between the NULL check and its subsequent dereference, resulting in use of a stale or NULL pointer in kernel context. No active exploitation has been identified (no CISA KEV listing, EPSS 0.18%), but the kernel-level impact class warrants prompt patching on affected stable branches.
The BPF signed loader in the Linux kernel fails to enforce map exclusivity before performing SHA-based integrity validation of metadata maps, allowing a local attacker with BPF privileges to race a mutation of the shared map's contents after the hash is computed but before validation completes. Systems running Linux kernel between commit fb2b0e290147ba01a53dfd92cf91058c9d2ee254 and the patched stable releases (6.18.40, 7.1.5, 7.2) are affected. Exploitation bypasses the integrity guarantees of the signed BPF loader, enabling the attacker to make the check pass on stale, attacker-controlled data; no public exploit exists and EPSS is 0.17% (6th percentile), indicating low current exploitation probability.
Out-of-bounds kernel memory reads in the Linux kernel's NTFS driver arise because ntfs_read_locked_inode() copies a resident $ATTRIBUTE_LIST into ni->attr_list via a plain memcpy() with no sanity checking, while only the non-resident path was ever validated by load_attribute_list(). A crafted NTFS volume with a malformed resident attribute list is then trusted by every subsequent walk (ntfs_external_attr_find(), ntfs_inode_attach_all_extents(), ntfs_attrlist_need()), which read fixed-header fields past the buffer. The fix factors per-entry validation into ntfs_attr_list_entry_is_valid()/ntfs_attr_list_is_valid() and applies it on the resident path and inside load_attribute_list() itself; no public exploit identified at time of analysis and EPSS probability is very low (0.15%).
Out-of-bounds slab read in the Linux kernel's legacy in-kernel NTFS driver lets a crafted on-disk $ATTRIBUTE_LIST leak or crash adjacent kernel heap memory when a malicious NTFS volume is mounted and read. The flaw is in ntfs_external_attr_find(), where a look-ahead attribute-list entry is dereferenced past the end of the kvmalloc'd buffer. There is no public exploit identified at time of analysis, EPSS risk is low (0.15%, 5th percentile), and it is not listed in CISA KEV.
Out-of-bounds kernel heap read in the Linux kernel's classic in-tree NTFS driver (`fs/ntfs/`) allows a local, low-privileged user to disclose kernel memory - and potentially chain to privilege escalation - by mounting a crafted NTFS image at the filesystem layer. The flaw is a u16 integer truncation in `ntfs_check_restart_area()` that silently defeats a page-size bounds check, causing `ntfs_check_log_client_array()` to dereference up to ~64 KiB beyond an allocated heap buffer using attacker-controlled on-disk values. No public exploit code exists and no active exploitation has been confirmed; EPSS is 0.15% (5th percentile), reflecting negligible observed exploitation pressure.
Heap and integer-overflow memory corruption in the Linux kernel's userspace perf tool (perf sched) lets a malicious perf.data file corrupt memory when parsed by register_pid(). An analyst who runs 'perf sched' against an attacker-supplied perf.data trace can trigger out-of-bounds heap writes, an unchecked strcpy into a 20-byte comm buffer, and denial of service, potentially leading to code execution in the context of the user running perf. A vendor fix is available; EPSS is low (0.18%) and there is no public exploit identified at time of analysis.
Out-of-bounds heap read in the Linux kernel's perf userspace tooling (perf tools) lets a crafted perf.data file trigger memory disclosure or a crash when parsed. The flaw sits in machine__resolve(), which trusts an attacker-controlled CPU index (al->cpu) from sample data and indexes env->cpu[] without validating it against env->nr_cpus_avail; a large index reads past the heap allocation, and values like 65536 truncate to int16_t and silently resolve to CPU 0. No public exploit is identified at time of analysis, and EPSS is low (0.18%, 7th percentile).
Use-after-free / stale-pointer race in the Linux kernel netfilter nf_conntrack_expect subsystem was resolved by replacing the per-expectation timer API with the conntrack garbage-collection worker. Under the old timer scheme, expectation removal could lose a race with an expiring timer (timer_del() returning false), leaving an expectation referencing an already-released exp->master conntrack, enabling stale-pointer access. The issue affects systems using connection-tracking helpers/expectations (e.g. FTP, SIP, or nft_ct expectations); no public exploit identified at time of analysis and it is not listed in CISA KEV, with a very low EPSS of 0.15% (5th percentile).
Availability denial in the Linux kernel's KVM ARM64 nested virtualization stack allows a guest VM to crash the host through improper Synchronous External Abort (SEA) handling when Stage 1 translation resolves a Guest Frame Number outside configured memory slots. Affected systems must run a vulnerable Linux 6.16-era kernel on ARM64 hardware with KVM nested virtualization explicitly enabled; fixed versions are 6.18.40, 7.1.5, and 7.2. No public exploit exists and no active exploitation is confirmed; EPSS stands at 0.18% (7th percentile), reflecting the niche attack surface.
NULL pointer dereference in the Linux kernel netfilter subsystem's xt_nat module allows a local attacker with low privileges to crash the kernel by instantiating SNAT or DNAT targets through the nft_compat compatibility layer using an unsupported bridge family, triggering a NULL dereference in nf_nat_setup_info(). Multiple stable kernel branches from 5.10 through 7.x are affected across numerous long-term support trees. No public exploit has been identified at time of analysis, and EPSS probability is very low at 0.18% (7th percentile); critically, the description itself notes the original crash was already mitigated by a prior upstream commit, making this patch a defense-in-depth hardening measure rather than a primary fix.
Symlink-based file clobbering in the Linux kernel's intel-speed-select daemon allows a local low-privileged user to redirect root-process writes to an attacker-chosen file by pre-positioning a symlink at the daemon's fixed /tmp pidfile path. Affected systems are those running Linux 5.18 through unpatched 6.x and 7.x branches on Intel Speed Select Technology hardware with the daemon active. No public exploit is identified at time of analysis and EPSS is low (0.17%, 7th percentile), but the attack is mechanically simple and requires only a local shell account.
Kernel stack disclosure and potential denial-of-service affect Linux systems with CXL hardware due to an off-by-8 size constant in the CXL RAS capability subsystem introduced in Linux 6.2. A local user who can trigger a CXL AER uncorrectable error and read tracefs can obtain up to 448 bytes of adjacent kernel stack data - potentially including code pointers and sensitive in-flight values - from the tracefs ring buffer. No public exploit identified at time of analysis; EPSS at 0.17% (6th percentile) reflects the niche CXL hardware dependency and local-only attack vector.
Use-after-free in the Linux kernel's UFS (Universal Flash Storage) core tracing subsystem allows a local attacker with tracing access to trigger a kernel crash or potentially achieve privilege escalation. The UFS trace event infrastructure stores raw pointers to the `hba` (Host Bus Adapter) structure in the trace ring buffer, then dereferences those pointers inside `TP_printk()` when `/sys/kernel/tracing/trace` is read - which may occur long after the underlying UFS device has been detached and its memory freed. No public exploit has been identified at time of analysis, and EPSS is 0.17% (6th percentile), indicating low near-term exploitation probability despite the high CVSS score.
Uninitialized-value access in the Linux kernel's HFS+ filesystem driver allows a local attacker with mount privileges to trigger kernel memory corruption or information disclosure by supplying a crafted disk image containing an invalid btree node_size. The flaw is reached during the mount path - specifically in hfsplus_bnode_find() while loading the HFS+ catalog B-tree - when a corrupted node_size value (e.g., 1) causes an excessively large offset to be passed to hfs_bnode_read_u16(), resulting in use of uninitialized stack memory. No public exploit has been identified and EPSS is 0.15% (5th percentile); upstream stable patches are available at git.kernel.org.
Race condition in the Linux kernel's hisi_sas v3 hardware driver triggers a kernel WARNING and potential memory corruption when SAS phy link reset and driver removal (rmmod) execute simultaneously. Specifically, during SAS phy bring-up, device_links_driver_bound sets the link status to DL_STATE_AVAILABLE, and a concurrent rmmod then causes __device_links_no_driver() to encounter an inconsistent device-link state. No public exploit exists and EPSS sits at 0.17% (6th percentile), reflecting this is a hardware-specific, privilege-intensive, timing-dependent flaw with very low exploitation likelihood in practice.
Out-of-bounds memory access in the Linux kernel's ARM SCMI firmware subsystem allows a local low-privileged attacker on ARM-based hardware to trigger kernel memory corruption via the scmi_power_name_get() function, which fails to validate the domain number supplied by external callers. Affected kernel versions span from the introduction commit 76a6550990e2 through multiple stable branches, with patches backported to LTS lines 5.15, 6.1, 6.6, 6.12, and 6.18. No public exploit code has been identified at time of analysis, and EPSS probability is very low at 0.17% (7th percentile), indicating no current attacker tooling interest despite the 7.8 CVSS score.
NULL pointer dereference in the Linux kernel IPv6 subsystem - specifically in `__in6_dev_stats_get()` - can crash the kernel and cause a denial of service when a physical network device is unregistered while IPv6 statistics are being collected. The vulnerability affects a wide range of stable kernel branches, from 4.19 through 7.x, and has been patched across all active LTS trees. No active exploitation is confirmed (not in CISA KEV) and EPSS at 0.18% (7th percentile) reflects low current real-world exploitation interest, though the ubiquitous deployment of the Linux kernel makes patch cadence important.
Invalid pointer dereference in the Linux kernel's RapidIO TSI721 driver allows an unauthenticated attacker on an adjacent RapidIO network to crash the kernel or corrupt memory by sending a crafted doorbell message. The root cause is a logic error in tsi721_db_dpc(): the 'found' flag is not reset at the start of each list_for_each() iteration, causing every doorbell after the first match to be treated as found, and causing list-end traversal with an invalid iterator pointer when no match exists. No public exploit exists and EPSS is 0.18% (7th percentile), consistent with the highly constrained physical attack surface; patches are available across multiple stable kernel branches.
Out-of-bounds write in the Linux kernel's OCFS2 cluster filesystem driver corrupts adjacent kernel memory when a low-privileged user unlinks a refcounted file whose refcount tree contains leaf blocks, triggering a fortify panic on hardened kernels. The root cause is an incorrect memset bound in `ocfs2_remove_refcount_extent()` arising from a union aliasing issue between `rf_records.rl_count` and `rf_list.l_tree_depth`. No public exploit or active exploitation has been identified; EPSS is 0.15% (5th percentile) and the vulnerability does not appear in CISA KEV, reflecting low real-world exploitation risk at time of analysis.
Unaligned memory access in the Linux kernel netfilter synproxy timestamp adjustment code can crash the kernel or degrade performance on strict-alignment CPU architectures when synproxy is actively configured. Systems running synproxy as a SYN-flood mitigation layer on architectures such as SPARC, classic MIPS, or ARM without hardware unaligned-access emulation are exposed to remote-triggered denial of service via crafted TCP packets. No active exploitation is confirmed (absent from CISA KEV) and EPSS at 0.17% (6th percentile) indicates negligible observed exploitation probability, though the network-reachable vector warrants timely patching on vulnerable platforms.
Out-of-bounds heap read in the Linux kernel's wcn36xx WiFi driver allows an adjacent-network attacker to corrupt Block Acknowledgment session state by sending crafted 802.11 frames that elicit a short firmware response. Kernels from 4.7 through pre-patch stable branches on devices equipped with Qualcomm WCN3660/WCN3620/WCN3680 WiFi hardware are affected. No public exploit code exists and no CISA KEV listing is present; EPSS of 0.17% (7th percentile) reflects negligible observed exploitation probability consistent with the hardware-specific attack surface.
Out-of-bounds stack read in the Linux kernel's netfilter flowtable (nf_flow_table / nft_dev_forward_path) affects the bridge VLAN-untag fast path, where a u8 num_encaps counter can underflow from 0 to 255 and cause the kernel to walk a fixed 2-entry encap[] array far past its bounds. Affected are kernels from 5.13 onward that use netfilter flowtable offload over bridge devices; the flaw leaks adjacent kernel stack memory into a route descriptor and copies a bogus encap count. No public exploit is identified at time of analysis, EPSS is low (0.15%), and it is not in CISA KEV.
Missing dma_resv lock acquisition before dma_buf_unpin() in the Linux kernel iommufd subsystem causes a kernel WARN on every IOAS destruction or unmap path that releases the last reference to a DMABUF-backed iopt_pages object. Affected are kernel versions from the commit introducing DMABUF pinning in iommufd (8c5f9645c389) through the fix commits in the 7.1 and 7.2 stable trees, with patches confirmed at Linux 7.1.5 and 7.2. No public exploit or active exploitation has been identified; EPSS is 0.15% (5th percentile), indicating negligible automated exploitation probability at time of analysis.
Null-pointer dereference in the Linux kernel's btrfs LZO decompression path can crash the kernel when reading a crafted compressed extent, causing a denial-of-service. Kernels in the range starting at commit a6e66e6f8c1b685e11b778bef614480a9c1a5278 through the two fix commits are affected across multiple stable branches (5.15 and later). No public exploit code or CISA KEV listing exists at time of analysis; the EPSS score of 0.15% (5th percentile) confirms this is not yet being exploited at scale. Exploitation requires the attacker to introduce a malformed btrfs filesystem image with LZO-compressed extents that the kernel then reads.
Memory corruption in the Linux kernel's net/sched fq_codel queueing discipline lets a local actor with traffic-control privileges trigger a wild kernel memory access and crash. When fq_codel drops packets during a peek operation, it calls qdisc_tree_reduce_backlog before restoring qlen; if qlen momentarily hits zero while peek still holds an skb, the parent class (e.g. qfq) is wrongly deactivated, producing a general-protection fault against a poisoned list pointer (0xdead000000000100 range) as seen under KASAN. No public exploit identified at time of analysis, EPSS is low (0.18%), and it is not in CISA KEV.
Race condition in the Linux kernel's ALSA OSS sequencer layer exposes local low-privilege attackers to kernel ring-buffer state corruption via unsynchronized reset operations. Specifically, snd_seq_oss_readq_clear() modifies qlen, head, and tail fields without holding q->lock, racing against reader and producer paths that correctly acquire the spinlock, potentially leaving stale or dropped MIDI events and corrupted readiness state. No public exploit identified at time of analysis; EPSS at 0.17% (6th percentile) indicates negligible current exploitation interest despite the CVSS 7.8 score reflecting theoretical kernel memory corruption severity.
Use-after-free and race condition vulnerabilities in the Linux kernel's tlclk (Telecom Clock) character driver expose local low-privileged users to potential kernel-space memory corruption, privilege escalation, or system crash. The module cleanup function tlclk_cleanup() frees alarm_events memory before awakening blocked waitqueue readers and before the switchover_timer completes, creating a use-after-free window during concurrent module unload. Additionally, the missing .owner field in file_operations allowed module unloading while userspace held the device open. No public exploit exists and EPSS is 0.18%, but patched kernel versions are confirmed across all active stable branches.
Use-after-free in the Linux kernel AppArmor subsystem's aa_replace_profiles function exposes kernelspace memory to corruption by a local low-privileged attacker. The defect arises from reading udata->size after aa_put_loaddata(udata) has released the reference - if that release triggers a free, the subsequent read constitutes a UAF that can be leveraged for privilege escalation or arbitrary kernel memory manipulation. EPSS sits at 0.18% (7th percentile) and no CISA KEV listing exists, indicating no confirmed widespread exploitation, though the local-access, low-complexity nature makes this a realistic intrahost threat on AppArmor-enabled systems.
Heap buffer overflow in the Linux kernel's Airoha (airoha_eth) network driver allows the packet-processing engine (PPE) flow-offload logic to write past an undersized allocation, corrupting kernel heap memory and crashing affected systems. The bug affects Linux 6.18.x through 6.18.39 and 6.19/7.x pre-release trees on hardware using the Airoha PPE flow-offload driver, and is triggered when airoha_ppe_foe_verify_entry() processes a flow hash at or above half the entry count. It is not in CISA KEV and has a low EPSS (0.18%), with no public exploit identified at time of analysis; impact is primarily denial of service.
The mt7925 WiFi driver (mt76 subsystem) in the Linux kernel fails to cancel a deferred work item on the device stop path, creating a 5-second race window during multi-link operation (MLO) power-save setup. If the mt7925 PCIe or USB device is torn down within that window, the surviving timer fires against a workqueue that has already been destroyed, triggering a kernel WARNING and potential crash. No public exploit has been identified; EPSS is 0.17% (6th percentile), and the bug requires local access to hardware running an affected kernel with MLO power-save active.
Out-of-bounds write in the Linux kernel mt76/mt7996 WiFi driver allows a malicious or malfunctioning MediaTek mt7996 chip to corrupt kernel heap memory. The vulnerability exists in mt7996_mcu_get_eeprom(), which derives a destination offset into dev->mt76.eeprom.data from a device-controlled field (event->addr, a __le32 in the MCU response) without bounding that offset before performing the EFUSE/EXT block copy. A compromised or deliberately crafted mt7996 device can trigger an OOB write of up to MT7996_EXT_EEPROM_BLOCK_SIZE bytes into kernel memory, with potential for privilege escalation or denial of service. No public exploit is identified at time of analysis and EPSS is 0.15%, consistent with the narrow attack surface requiring hardware-level adversarial control.
Out-of-bounds memory read in the Linux kernel mt76/mt7996 Wi-Fi driver allows a local attacker with ability to supply a truncated EEPROM firmware file to trigger kernel memory disclosure or crash during driver initialization. The driver unconditionally copies and validates the default EEPROM firmware without first checking its length against the expected MT7996_EEPROM_SIZE constant, so a file shorter than that threshold causes reads past the end of the allocated firmware buffer. No public exploit has been identified at time of analysis; EPSS sits at 0.17% (6th percentile), reflecting the hardware-gated, local-access constraint.
Slab-use-after-free in the Linux kernel vsock/virtio transport driver allows a local attacker to trigger kernel memory corruption by exploiting a work-item flush ordering bug during device removal. The virtio_vsock_remove() path flushes work items without respecting producer-to-consumer dependencies (tx_work → send_pkt_work → rx_work), allowing kfree(vsock) to race with a newly queued rx_work item, as confirmed by KASAN reporting a UAF read in virtio_transport_rx_work. No public exploit exists and no active exploitation has been identified; EPSS is 0.17% (6th percentile). Patches are available in stable releases 6.12.109, 6.18.50, 7.2.4, and 7.3-rc1.
Out-of-bounds kernel heap write in the Linux kernel's DS28E17 1-Wire-to-I2C bridge driver allows a local attacker controlling a malicious I2C slave device to write up to 222 bytes past a 34-byte kernel buffer. The driver's w1_f19_i2c_read() unconditionally trusts a device-supplied length byte (0-255) on I2C_M_RECV_LEN transactions, but the caller buffer is only I2C_SMBUS_BLOCK_MAX + 2 bytes; the SMBus core's own BLOCK_MAX check runs only after the overwrite has already occurred. No public exploit has been identified at time of analysis; EPSS sits at 0.17%, reflecting the niche hardware prerequisite.
Improper sysctl table placement in the Linux kernel allows a local low-privileged user to modify the global `cad_pid` setting - which controls which process receives the Ctrl-Alt-Delete console signal - by abusing unprivileged user and PID namespace creation. A non-root user can call `unshare(CLONE_NEWUSER|CLONE_NEWPID)` to gain apparent root privileges in a child namespace and then overwrite the globally-scoped `/proc/sys/kernel/cad_pid`, even though `kill_cad_pid()` operates exclusively in the root namespace. No public exploit is identified at time of analysis; EPSS stands at 0.20% (10th percentile), and no CISA KEV listing exists.
Use-after-free in the Linux kernel's Smack LSM `smack_file_send_sigiotask()` function allows a local attacker with low privileges to trigger kernel memory corruption by racing credential pointer changes on a non-current task. The function incorrectly accessed both `tsk->cred` (subjective credentials, unprotected) and `__task_cred(tsk)` (objective credentials) on the same task; because a task may change its own `->cred` pointer at any time without synchronization, the first access can race with a credential transition, yielding a freed `struct cred` deref. The author confirmed KASAN-reported UAF reproduction and verified the fix. No public exploit exists and EPSS is low at 0.17%, but the CVSS-assessed local impact (C:H/I:H/A:H) reflects the potential for privilege escalation on affected kernels.
Use-after-free in the Linux kernel's ksmbd in-kernel SMB3 server lets any authenticated SMB client holding a durable batch oplock corrupt kernel memory during oplock-break notification. smb2_oplock_break_noti() reads opinfo->conn without a lock and dereferences it after two sleep-capable allocations; if the durable handle owning the oplock is disconnected concurrently, the connection is freed and a racing break from another connection resurrects the stale pointer, leading to a use-after-free in ksmbd_conn_write(). No public exploit identified at time of analysis, and EPSS is low (0.17%), consistent with a race-dependent, DoS-leaning memory-safety bug rather than a turnkey RCE.
The krb5 crypto subsystem in the Linux kernel fails to zero derived Kerberos key material before freeing memory buffers, leaving sensitive cryptographic keys resident in freed slab allocator objects. Both `crypto_krb5_prepare_encryption()` and `crypto_krb5_prepare_checksum()` call plain `kfree()` instead of the security-aware `kfree_sensitive()` wrapper, which would first zero the allocation. Systems using Kerberos-authenticated kernel services - primarily NFSv4 with sec=krb5 or CIFS/SMB with Kerberos - on kernel versions from commit 3936f02b through the stable fixes are affected; no public exploit or active exploitation has been identified.
Unauthorized cryptographic hardware access in KVM for s390 (IBM Z) nested virtualization allows a low-privileged nested guest to access AP queues (hardware crypto devices) that were explicitly revoked from its allocation. When the KVM VSIE subsystem shadows a format0 APCB (Adjunct Processor Control Block) from a crycb type 0 or 1 structure, it only copies bits 0-63 but leaves bits 64-255 unchanged from whatever stale state existed in the vsie shadow page. A nested (L2) guest exploiting this retains access to cryptographic devices beyond those granted by the host hypervisor, potentially exposing cryptographic keys and operations belonging to other workloads. No public exploit has been identified at time of analysis and no CISA KEV listing exists.
Use-after-free in the Linux kernel Bluetooth ISO stack allows an adjacent unauthenticated attacker to corrupt kernel memory and potentially execute arbitrary code. The flaw is a race condition in iso_conn_ready(): when a BIS listener socket is concurrently closed while an incoming Bluetooth Isochronous connection is being processed, a child socket is allocated that holds a dangling pointer to the now-freed parent socket, which is later dereferenced during disconnect via iso_chan_del() and bt_accept_unlink(). Patches are available across multiple stable kernel branches (6.12.109, 7.2.4, 6.18.50, and 7.3-rc1); no public exploit code or active exploitation has been identified at time of analysis.
Incorrect permission assignment on a critical resource in Pardus LightDM Greeter allows a local low-privileged user to read sensitive authentication material or tamper with greeter configuration, achieving high confidentiality and integrity impact without elevated rights. All versions before 0.4.15 of the greeter - a graphical login component shipped with Pardus, the Turkish government-backed Linux distribution maintained by TÜBİTAK BİLGEM - are affected. No public exploit or active exploitation has been identified; a vendor-released patch is available. No special configuration is required beyond having a local user account on an affected system.
Out-of-bounds buffer access in the Linux kernel's synaptics-rmi4 driver exposes systems with Synaptics RMI4 touchpad hardware to kernel memory corruption triggered by a copy-paste typo in F55 electrode initialization. On affected hardware where the receiver (RX) electrode count exceeds the transmitter (TX) count, the incorrectly propagated TX value causes F54 diagnostic routines to calculate an inflated report buffer size, enabling potential OOB reads or writes in kernel space. Patched stable releases are available across all maintained kernel branches; no public exploit code or active exploitation (CISA KEV) has been identified, and EPSS remains at 0.21%.
Race condition in the Linux kernel's ovpn (kernel-native OpenVPN) module allows a workqueue callback to continue executing within module text after that text has been freed during module teardown, creating a use-after-free condition in kernel space. The flaw exists because ovpn queues work items on the global system workqueue rather than a module-owned queue, leaving no driver-controlled drain point to guarantee all callbacks have exited before the module's code segment is released. Systems actively using the kernel-native ovpn module are at risk of kernel memory corruption or crash during module unload; no public exploit has been identified at time of analysis and EPSS is 0.20%.
NULL pointer dereference in the Linux kernel's psxpad-spi driver crashes the kernel when system suspend is triggered on hardware using SPI-connected PlayStation controllers. The probe() function in drivers/input/joystick/psxpad-spi.c omits the spi_set_drvdata() call that stores per-device state, so psxpad_spi_suspend() unconditionally dereferences a NULL pointer on suspend entry, causing a kernel panic. Patches are available across all active stable kernel branches (5.10 through 7.2); EPSS is 0.21% and no active exploitation has been identified.
Uninitialized pointer dereference in the Linux kernel's MediaTek GPU power-domain driver (`pmdomain/mediatek/mfg`) can trigger a kernel fault or incorrect OPP (Operating Performance Point) configuration on first device attachment. The `prev_o` variable in `mtk_mfg_attach_dev()` is read in a conditional branch on the first loop iteration before ever being assigned, meaning it holds an indeterminate stack value; if that value is non-NULL, the kernel dereferences a stale or garbage pointer. Affected versions span stable kernel trees from commit f08e7a4e8d6a through the fixed points in 7.1.10, 7.2, and 6.19. No public exploit code and no CISA KEV listing are present; EPSS at 0.19% (9th percentile) reflects minimal real-world exploitation interest.
Use-after-free in the Linux kernel's MediaTek power domain driver exposes kernel memory to potential corruption via a dangling device-tree node pointer. In scpsys_get_bus_protection_legacy(), two error paths call of_node_put() to release infracfg and SMI device-tree node references before those nodes are passed to dev_err_probe() with the %pOF format specifier; if the put drops the last reference, the formatter dereferences freed memory. Vendor patches are available for Linux 6.18.46, 7.1.10, and 7.2, and EPSS exploitation probability sits at 0.20% (10th percentile) with no confirmed active exploitation.
Out-of-bounds memory read in the Linux kernel's DRM HDMI connector subsystem allows a local, low-privileged user to potentially leak up to 32 bytes of adjacent kernel heap memory or trigger a page fault leading to kernel crash. The flaw exists in a helper function that copies audio infoframe data using the destination buffer size (60 bytes) rather than the source structure size (28 bytes), reading 32 bytes beyond the source allocation. No public exploit code exists, and EPSS sits at the 10th percentile; however, the availability impact is real - the overread can cross a page boundary and cause an access violation.
Out-of-bounds memory access in the Linux kernel's Loongson2 MMC driver allows a local authenticated user to corrupt kernel memory through incorrect scatterlist indexing in the mmc: loongson2 subsystem. The functions `ls2k0500_mmc_reorder_cmd_data()` and `ls2k2000_mmc_reorder_cmd_data()` use `for_each_sg()` to iterate a scatterlist but then incorrectly re-index the current `sg` pointer as if it were an array base (using `&sg[i]`), causing access to wrong or out-of-bounds scatterlist entries. This memory corruption can lead to full kernel compromise - confidentiality, integrity, and availability loss - on systems using Loongson LS2K0500 or LS2K2000 SoCs equipped with MMC storage. No public exploit has been identified at time of analysis.
Out-of-bounds memory reads in the Linux kernel's drm/amdkfd CRAT table parser allow a local attacker to leak kernel memory and potentially crash the system on AMD GPU/APU-equipped hosts. The CRAT (Component Resource Affinity Table) subtype parser validates that a subtype header fits within the image buffer but fails to verify that the advertised subtype length field also stays within bounds, enabling kfd_parse_subtype() to cast the header pointer beyond valid memory when a malformed CRAT table is supplied. No public exploit has been identified at time of analysis; EPSS is 0.19%, placing this in the 9th percentile.
Out-of-bounds table access in the Linux kernel fp9931 regulator driver exposes kernel memory to corruption via a malformed VPOS/VNEG voltage selector lookup table. The fp9931 driver's VPOSNEG_table[] contains two defects: a duplicate 7.04V entry that shifts all subsequent selector mappings by one, and a truncated table of only 41 entries instead of the required 64, meaning any selector value above 0x28 triggers an out-of-bounds access in kernel memory. Devices incorporating the FP9931 PMIC (a display-panel power regulator) running affected kernel versions are vulnerable; exploitation probability is very low (EPSS 0.20%, 10th percentile) with no public exploit and no confirmed active exploitation.
Out-of-bounds kernel memory read in the Linux kernel DRM log subsystem allows a local low-privileged user to potentially disclose kernel memory contents or crash the system. The flaw resides in drm_log_draw_kmsg_record(), where an unsigned integer underflow on a zero-length message causes an array access at offset UINT_MAX (0xFFFFFFFF) rather than a valid buffer position. No public exploit exists and EPSS sits at 0.20% (10th percentile), indicating low observed exploitation interest, though the kernel DRM panic-display path is reachable on any system with a GPU using the DRM framework.
Type-confusion memory access in the Linux kernel BPF subsystem allows a local attacker with BPF-capable privileges to read or corrupt kernel memory via the bpf_tcp_gen_syncookie and bpf_tcp_check_syncookie helpers. Both helpers accept a generic sock_common pointer (ARG_PTR_TO_BTF_ID_SOCK_COMMON) but dereference fullsock-specific fields without first confirming the socket is in TCP_LISTEN state, meaning a mini-socket passed to either helper causes an out-of-bounds struct field access. No public exploit has been identified and EPSS sits at 0.20% (10th percentile), though the C:H/I:H CVSS impact signals the potential to compromise kernel memory integrity if exercised by a sufficiently privileged local process.
Use-after-free and race condition in the Linux kernel's amba-pl011 ARM UART serial driver during DMA teardown allows a local attacker to corrupt kernel memory, potentially gaining arbitrary code execution or causing a denial of service. The flaw exists because dmaengine_terminate_all() returns without waiting for in-flight callbacks to complete, enabling the TX DMA callback to dereference already-freed TX buffer memory; a parallel race exists in the RX path where the poll timer accesses RX buffers without holding the port lock. Patches are available across multiple stable kernel branches; no public exploit code or active exploitation (KEV) has been identified at time of analysis.
Out-of-bounds array access in the Linux kernel's Thunderbolt driver exposes local low-privileged users to potential kernel memory corruption and privilege escalation. The flaw in tb_consumed_dp_bandwidth() sizes the group_reserved[] array at MAX_GROUPS entries (indices 0 through MAX_GROUPS-1) but uses Group IDs directly as indices, where valid IDs run from 1 through MAX_GROUPS - causing an off-by-one that reads and writes one element past the array boundary when the highest bandwidth group is processed. Patches are available across multiple stable kernel branches (6.12.x, 6.18.x, 7.1.x, 7.2), and no public exploit code has been identified at time of analysis.
Out-of-bounds kernel memory reads in the Linux kernel's ovpn (in-kernel OpenVPN) driver allow a local attacker with low privileges to leak kernel memory by abusing a missing ownership check on the sk_user_data socket field. The driver dereferences sk_user_data as an ovpn-internal structure without first confirming that encap_type identifies the socket as ovpn-owned, so when BPF SOCKMAP or another subsystem has populated sk_user_data with a different pointer type, ovpn misinterprets that memory and reads out of bounds. Affected kernels span 6.16 through pre-patch stable releases; no public exploit has been identified and EPSS sits at 0.21% (11th percentile), but kernel memory disclosure can seed further privilege escalation.
Btrfs in the Linux kernel fails to reinitialize inode address-space mapping flags and minimum folio order when re-reading previously evicted cached inodes, causing a kernel assertion failure and system crash (denial of service). The defect surfaces only when btrfs is mounted with a block size larger than the host memory page size - a non-default but valid configuration - and manifests after a create/evict/re-read inode cycle. No public exploit code exists and EPSS is 0.20% (10th percentile), reflecting negligible real-world exploitation probability beyond accidental triggering.
Use-after-free in the Linux kernel's pata_sl82c105 PATA bridge driver allows a local low-privileged user to potentially achieve kernel memory corruption leading to privilege escalation on systems equipped with the SL82C105 PCI bridge chip. The defect was introduced by commit 44c10138fd4b, which replaced a PCI configuration-space read with direct access to the cached revision field of a PCI device struct - but left that access after the reference was dropped via pci_dev_put(), creating a window where the bridge struct may be freed before the read occurs. Patches have been backported across multiple long-term stable kernel branches; no public exploit code or active exploitation has been identified at time of analysis.
Out-of-bounds write in the Linux kernel's `dev_validate_header()` network function allows a local process holding `CAP_SYS_RAWIO` to corrupt kernel memory by sending a raw packet with a short link-layer header while the target network device is concurrently reconfigured to increase `hard_header_len`. The `memset` zero-padding operation writes past the skb headroom reserved at allocation time, producing a silent memory corruption that is worse than the pre-existing `skb_under_panic()` it masks. Patches are available across multiple stable kernel branches; EPSS stands at 0.24% with no public exploit or CISA KEV listing.
Local privilege escalation / host memory corruption in the Linux kernel's KVM x86 shadow-MMU allows a malicious or buggy guest to trigger a slab use-after-free on the KVM host. When KVM derives a child shadow page's role from an invalid/obsolete parent root, it fails to clear role.invalid, violating the invariant that invalid pages stay off the active MMU list; __kvm_mmu_prepare_zap_page() then uses list_add() instead of list_move(), corrupting the list and freeing a shadow page that is still referenced, producing a KASAN slab-use-after-free in __kvm_mmu_get_shadow_page. There is no public exploit identified at time of analysis and EPSS is low (0.21%), but the fix is a hardening/defense-in-depth patch that also adds a WARN when an invalid parent is encountered.
Out-of-bounds kernel heap write in the Linux kernel's GRO (Generic Receive Offload) BIG TCP path allows corruption of memory before skb->head when aggregating oversized (>64KB) packets. The flaw stems from skb_gro_receive() using a loose headroom check introduced by the IPv4 BIG TCP support commit (b1a78b9b9886); crafted frames - for example injected via AF_PACKET with a MAC header under 8 bytes - pass validation, so ipv6_gro_complete()'s memmove() for the temporary HBH jumbo header writes before skb->head and wraps skb->mac_header. It also let software VLAN and encapsulated flows (SIT/IPv6-in-IPv4) aggregate beyond 64KB. No public exploit is identified at time of analysis and EPSS is low (0.19%), and the issue affects only older stable branches (e.g. 6.18.y), not mainline 7.0+.
Boot registry parameter injection in IGEL OS 12 (before 12.7.6) and IGEL OS 11 (before 11.11.150) allows an attacker with physical access to execute arbitrary Linux kernel command-line parameters by writing to an unencrypted, unsigned configuration partition that the signed bootloader reads at startup. The attack is particularly dangerous because it does not alter the measured boot code path, meaning TPM PCR attestation does not detect the tampering - effectively defeating the trust assumptions of the secure boot and full-disk encryption stack. A publicly available exploit script and a DEF CON 34 presentation detail the technique; no CISA KEV listing has been issued at time of analysis, indicating exploitation has not been confirmed at scale.
vmclock in the Linux kernel exposes a shared ABI memory page that a low-privileged guest process can upgrade from read-only to writable using mprotect(), allowing direct corruption of host-maintained timekeeping fields including sequence counters, UTC time, and TSC offsets. Affected deployments are virtualized Linux guests running kernels prior to patched stable releases 6.18.47, 7.2.1, and 7.1.11, where the vmclock miscdevice driver fails to clear VM_MAYWRITE on read-only mmap paths. No public exploit code has been identified at time of analysis, and EPSS at 0.15% (5th percentile) reflects low observed exploitation pressure despite a CVSS 8.8 score driven by the scope-changing guest-to-host integrity impact.
Out-of-bounds memory write in the Linux kernel's device tree reserved memory subsystem allows an attacker with control over device tree content to corrupt kernel memory at boot time, with theoretical full kernel compromise (C:H/I:H/A:H). The fdt_scan_reserved_mem() function writes past the end of a fixed-size local array when a device tree blob defines more dynamically-placed /reserved-memory subnodes than MAX_RESERVED_REGIONS allows. Despite a CVSS score of 8.4, exploitation is heavily constrained by the requirement to modify device tree content before boot - a capability requiring privileged firmware access - and EPSS at 0.16% (5th percentile) reflects negligible observed exploitation probability. No public exploit has been identified and the vulnerability is absent from CISA KEV.
Insufficient validation of S1G (802.11ah/Wi-Fi HaLow) Target Wake Time setup frames in the Linux kernel's mac80211 subsystem allows an unauthenticated adjacent-network attacker to submit a malformed individual TWT agreement whose parameter block is shorter than the full struct ieee80211_twt_params. The driver callback drv_add_twt_setup() and associated kernel tracepoint both consume the complete parameters structure regardless of the truncated length, potentially triggering kernel memory corruption, out-of-bounds reads exposing sensitive kernel memory, or a denial-of-service crash. No public exploit code has been identified, CISA KEV listing is absent, and patches are confirmed across seven stable kernel branches; real-world exposure is substantially narrowed by the requirement for S1G hardware.
Dangling pointer dereference in the Linux kernel Bluetooth ISO subsystem exposes systems running kernel versions prior to 6.18.44, 7.1.8, and 7.2 to potential kernel memory corruption from adjacent Bluetooth attackers. After iso_conn_del() is invoked, ISO sockets may continue to dereference the freed hcon (HCI connection) pointer due to imprecise reference-counting logic, creating a use-after-free-class condition in kernel space. Despite a high NVD CVSS score of 8.8, the EPSS rating of 0.15% (5th percentile) and absence from CISA KEV indicate no public exploit or observed active exploitation at time of analysis.
Deadlock in the Linux kernel's iomap subsystem allows local attackers to cause a denial of service by exhausting the shared bioset used by both iomap_split_ioend and its input bios. The circular dependency in bioset allocation halts I/O completion on iomap-backed filesystems (XFS, ext4 direct I/O) and can hang the affected system. No active exploitation has been confirmed (not in CISA KEV) and the EPSS probability is very low at 0.15% (5th percentile), but the impact on availability is total for the affected I/O path.
Bitmap overflow and incorrect global accounting in the Linux kernel's percpu-km memory allocator (`mm/percpu-km`) allow a local low-privileged attacker on SMP/NUMA systems to corrupt kernel memory, with potential for privilege escalation or kernel crash. Two separate commits introduced the flaws: a63d4ac4ab609 caused `pcpu_create_chunk()` to write beyond the `chunk->populated` bitmap when `nr_units > 1`, and b539b87fed37f introduced the companion `pcpu_nr_empty_pop_pages` accounting error. Fixes have been backported to eight stable kernel branches (5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103, 6.18.44, 7.1.8, 7.2); no public exploit has been identified at time of analysis.
Out-of-bounds read in the Linux kernel SCTP subsystem leaks up to four bytes of receive-buffer tail memory to remote unauthenticated attackers via a malformed INIT chunk. When an Adaptation Layer Indication parameter is sent with only its 4-byte header (omitting the mandatory 32-bit Adaptation Code Point), the kernel reads past the declared parameter boundary and copies those bytes into the state cookie of the INIT ACK response, exposing them to the peer. No public exploit has been identified and EPSS of 0.16% (6th percentile) indicates low exploitation probability, though the unauthenticated, network-accessible attack surface on any SCTP-enabled system warrants prompt patching.
Use-after-free in the Linux kernel ALSA PCM subsystem allows a local low-privilege attacker to corrupt kernel memory by exploiting a race between snd_pcm_drain() and snd_pcm_unlink() on linked streams. When a drain wait terminates by signal or timeout while group membership is concurrently modified by an unlink, a stack-allocated wait queue entry is left queued on a freed peer stream's sleep list; a subsequent wake_up() call then dereferences that freed stack frame. No public exploit code or CISA KEV listing exists at time of analysis; the EPSS of 0.16% (6th percentile) reflects low near-term exploitation probability.
Use-after-free in the Linux kernel's IPVS (IP Virtual Server) connection-synchronization path allows corruption of the connection hash table on backup directors running the IPVS sync daemon. When a synced connection is bound to a destination that carries the IP_VS_CONN_F_ONE_PACKET flag, expiry logic wrongly skips unlinking the conn_tab node, leaving a stale hash entry pointing at a freed struct ip_vs_conn. There is no public exploit identified at time of analysis and EPSS is very low (0.16%), so despite the auto-assigned 9.8 rating this is a memory-safety defect in a specialized load-balancing feature rather than a broadly weaponizable RCE.
Restriction bypass in the Linux kernel's io_uring subsystem allows a local low-privileged user to shed per-task io_uring security restrictions by executing exec(). When a task that has established io_uring restrictions calls exec(), the kernel's exec cancellation path invokes __io_uring_free(), which incorrectly frees both the task context and the per-task restriction simultaneously. Any io_uring ring created by the post-exec process is then entirely unrestricted, defeating sandbox and policy enforcement intended to constrain io_uring operations. No public exploit has been identified at time of analysis, but the CVSS score of 8.4 with Changed Scope (S:C) reflects that the bypass can expose confidentiality and integrity of resources guarded by the dropped restrictions.
The spi-qpic-snand NAND flash driver in Linux kernel 6.18 and later contains a command-ordering defect that causes every SET_FEATURE write to apply the previous operation's value rather than the intended one, producing an off-by-one effect. On Qualcomm IPQ5018-based hardware (confirmed on TP-Link Archer AX55 v1 with ESMT F50L1G41LB flash), this defect became destructive in v6.18 when SPI-NAND OTP support was introduced: the 'disable OTP mode' call erroneously leaves CFG_OTP_ENABLE set permanently, causing all subsequent flash reads to return OTP area content and all writes to fail with -EIO, rendering the device unbootable. No public exploit identified at time of analysis; EPSS of 0.15% (5th percentile) correctly reflects that this is a driver logic defect rather than a traditionally attacker-controllable vulnerability.
Integer truncation in the Linux kernel s390/dasd ECKD driver exposes IBM Z systems to a heap buffer overflow via a caller-controlled track range supplied to dasd_eckd_check_device_format(). The root cause is that fmt_buffer_size is declared as int while the buffer-size expression evaluates at size_t width, causing the result to be silently truncated on assignment; kzalloc() then allocates a buffer far smaller than needed, while the subsequent channel program builder operates on the untruncated track count and writes past the allocation. Systems running unpatched kernels before 6.6.151, 6.12.103, 6.18.44, 7.1.8, or 7.2 on s390 architecture face potential kernel heap corruption with consequences ranging from denial of service to local privilege escalation. No public exploit code exists and this vulnerability has not been added to the CISA KEV catalog at time of analysis.
Heap out-of-bounds memory access in the Linux kernel s390/zcrypt subsystem exposes EP11 crypto card administrative paths to local low-privileged users. The flaw resides in the domain value upper-limit check processed when sending EP11 CPRBs (Control Program Request Blocks) through custom zcrypt device nodes - the missing AP_DOMAINS (256) ceiling allows an attacker-supplied domain index to reach heap memory beyond the `perms->adm` structure. No public exploit code has been identified and this is not listed in CISA KEV, but the CVSS 7.8 local vector and confirmed multi-version patch backports across stable kernel branches indicate the Linux security team treats the impact as high. EPSS at 0.16% (6th percentile) reflects the platform-specific nature of the flaw.
Uninitialized receive buffer allocation in the Linux kernel's CAN J1939 transport layer exposes residual kernel heap memory to J1939 session participants. The function j1939_session_fresh_new() allocates a buffer without zeroing it, meaning any system running a CAN-capable Linux kernel with J1939 transport support may leak prior heap contents to peers exchanging Extended Transport Protocol (ETP) messages. No public exploit has been identified at time of analysis, and EPSS sits at 0.16% (6th percentile), consistent with a low-exploitation-probability kernel information-disclosure flaw in a specialized networking subsystem.
Out-of-bounds read and write vulnerabilities in the Linux kernel's softing CAN driver `fw_parse()` function allow a local low-privileged attacker to corrupt kernel DPRAM memory by supplying a crafted firmware image. Affected kernels span from 2.6.38 through pre-patch stable branches (5.10.x, 5.15.x, 6.1.x, 6.6.x, 6.12.x, 6.18.x, 7.1.x, and 7.2), with fixes backported across all active stable trees. No public exploit or active exploitation has been identified at time of analysis.
Memory corruption in the Linux kernel's VMware graphics (vmwgfx) DRM driver allows a local, low-privileged user on a VMware guest system to corrupt MOB (Memory Object Buffer) allocation metadata, leading to out-of-bounds reads or writes with high confidentiality, integrity, and availability impact. A field-naming bug in vmwgfx_resource.c writes boolean literals (0/false and 1/true) to the guest_memory_size unsigned-long field instead of the adjacent guest_memory_dirty bitfield, causing subsequent size-dependent operations to compute zero-length or wrap-around memory ranges on the MOB bitmap. No public exploit has been identified at time of analysis; EPSS is very low at 0.17% (6th percentile), though the CVSS 7.8 score reflects meaningful severity if triggered locally on a VMware guest.
Out-of-bounds memory corruption in the Linux kernel's vmwgfx DRM driver (vmw_external_bo_copy()) allows a local attacker with low-privilege DRM access to corrupt kernel memory via a crafted atomic display commit using an imported dma-buf framebuffer. Two distinct code paths are vulnerable: the equal-stride memcpy path suffers unsigned integer underflow when caller-supplied offsets exceed the buffer object size, and the non-equal-stride row-by-row path performs no bounds validation at all, allowing the copy loop to walk arbitrarily past the vmap end. Vendor-released patches are available across multiple stable kernel branches; no public exploit has been identified at time of analysis.
Out-of-bounds memory access in the Linux kernel's ltc4282 hwmon driver exposes systems with this hardware monitor to kernel memory disclosure or destabilization via the VGPIO minimum alarm voltage sysfs read path. A missing return statement in the driver causes the kernel to access memory beyond intended bounds when a local user reads the VGPIO channel's minimum alarm voltage attribute. Patch versions are available across multiple stable branches; no public exploit exists and EPSS sits at 0.17% (6th percentile), indicating very low current exploitation pressure despite the 7.8 CVSS score.
Denial of service in the Linux kernel's MediaTek mtk_eth_soc Ethernet driver: mtk_poll_controller() passed a net_device pointer to mtk_handle_irq_rx(), which expects a struct mtk_eth pointer (the value registered as the request_irq cookie). When CONFIG_NET_POLL_CONTROLLER is enabled and the ndo_poll_controller path is exercised (e.g. via netconsole/netpoll), the resulting bad-pointer dereference crashes the kernel. Only devices using the MediaTek SoC Ethernet driver are affected; there is no public exploit identified at time of analysis and EPSS is low (0.17%, 6th percentile).
Out-of-bounds slab write in the Linux kernel idpf network driver lets a malicious or compromised control plane (a PF or a hypervisor's device model) corrupt kernel heap memory during interrupt-vector setup. idpf_get_reg_intr_vecs() fills the reg_vals[] array bounded only by per-chunk num_vectors from a VIRTCHNL2_OP_ALLOC_VECTORS reply, which is never reconciled against the smaller num_allocated_vectors used to size the allocation, so a reply whose chunk counts sum higher writes struct idpf_vec_regs entries past the buffer. It carries a CVSS of 9.3, but EPSS is only 0.15%, it is not on CISA KEV, and there is no public exploit identified at time of analysis.
Use-after-free in the Linux kernel Bluetooth HCI sync subsystem exposes systems running vulnerable kernel versions (6.6.51-pre-6.7 and 6.8.9-pre-6.9) to potential kernel-context memory corruption from an adjacent attacker with no privileges required. The race condition occurs when hci_connect_acl/le_sync() callbacks dereference a freed hci_conn object during concurrent connection teardown, yielding a theoretical path to arbitrary code execution or kernel panic. No public exploit code has been identified at time of analysis, and EPSS at 0.15% (5th percentile) indicates very low observed exploitation activity.
Null pointer dereference in the Linux kernel's SCSI target iblock driver crashes the kernel when processing Persistent Reservation PREEMPT or RELEASE operations against storage backends with unimplemented PR hooks. Systems running the kernel as an iSCSI target are vulnerable - an attacker who can issue SCSI Persistent Reservation commands can trigger a kernel panic, causing a complete denial of service. No public exploit has been identified and EPSS sits at 0.17% (6th percentile), but patches are available across multiple stable branches and should be applied promptly on iSCSI target infrastructure.
Out-of-bounds vmemmap read in the Linux kernel's mm/util snapshot_page() crashes or leaks kernel memory during page isolation on memory-remove paths. The function incorrectly reads __page_2 when nr_pages > 1 rather than the correct threshold of nr_pages > 2, causing an illegal access into an adjacent, unmapped vmemmap section when an order-1 folio sits at a vmemmap section boundary. This was observed producing a kernel oops on ppc64le systems during DLPAR memory remove on a 22 TB LPAR. No public exploit is identified and EPSS is 0.17%, but the defect can cause a local denial-of-service or kernel memory disclosure. Patches are available across multiple stable kernel branches.
Denial-of-service in the Linux kernel's KVM subsystem on IBM Z (s390) mainframes stems from an unchecked airq_iv_create() return value in the zPCI adaptive-interrupt path. When AIBV allocation fails, zdev->aibv is left NULL and later dereferenced in kvm_zpci_set_airq(), crashing the host kernel. No public exploit identified at time of analysis and it is not in CISA KEV; EPSS is low at 0.17% (7th percentile), consistent with a hard-to-trigger, resource-exhaustion-dependent bug rather than a broadly weaponizable flaw.
Use-after-free in the Linux kernel Bluetooth SCO subsystem allows an adjacent unauthenticated attacker to corrupt freed kernel memory by exploiting a reference-counting race between socket close() and Bluetooth controller Disconnection Complete events. The race causes sco_conn_del() to perform a double put on a kref, confirmed by KASAN as slab-use-after-free, with potential to escalate privileges or crash the system. No public exploit or CISA KEV listing exists; EPSS is 0.17% (6th percentile), consistent with the race condition complexity limiting practical exploitation.
Incorrect unit conversion in the RISC-V memory management subsystem causes vmemmap_start_pfn to be computed with a physically misaligned base, violating the mask-alignment requirement for compound_info encoding in the sparse memory model. Linux kernel versions incorporating commit 476849b0fba4 on RISC-V hardware where DRAM base is not aligned to MAX_FOLIO_NR_PAGES × PAGE_SIZE are affected - a condition confirmed on QEMU virt machines and potentially other RISC-V platforms. CVSS 7.8 (AV:L/PR:L/C:H/I:H/A:H) reflects potential local privilege escalation via kernel memory corruption; EPSS of 0.17% (7th percentile) and no CISA KEV listing indicate no observed exploitation activity. No public exploit is identified at time of analysis.
Use-after-free in the Linux kernel's VXLAN transmit path (vxlan_xmit) lets a stale Ethernet header pointer be dereferenced after route_shortcircuit() calls pskb_may_pull() and reallocates skb->head, corrupting or reading freed memory when accessing eth->h_dest. The flaw affects systems using a VXLAN overlay interface and is most realistically a denial-of-service (kernel crash) with potential information disclosure; no public exploit identified at time of analysis and EPSS is low (0.18%). It is not listed in CISA KEV and no proof-of-concept is known.
Use-after-free in the Linux kernel's AMD MP2 I2C driver (i2c-amd-mp2) enables local low-privileged users to corrupt kernel memory, potentially achieving privilege escalation or system crash on AMD hardware. The flaw occurs during driver probe: when i2c_add_adapter() fails, devres frees the platform I2C context, but the MP2 PCI driver retains a stale pointer in its IRQ and system-sleep callback table, allowing subsequent dereference of freed memory. No public exploit exists and EPSS is 0.18% (7th percentile), reflecting the hardware-specific and error-path-dependent nature of this flaw; vendor-released patches are available across all major stable kernel branches.
Race condition and error-handling flaws in the i2c-imx I2C controller driver allow a NULL pointer dereference via the kernel interrupt handler on NXP i.MX SoC-based systems. The vulnerability affects multiple stable kernel branches (5.15 through 7.x) and is triggered when I2C slave registration fails partway through a PM runtime resume, leaving a stale or NULL pointer that the shared IRQ handler can dereference concurrently. The realistic impact is a kernel panic causing system unavailability; no public exploit exists and EPSS is 0.17%, consistent with no observed active exploitation.
Race condition in the Linux kernel's driver core `dev_has_sync_state()` exposes a TOCTOU (Time-of-Check Time-of-Use) flaw allowing local low-privileged users to potentially trigger kernel memory corruption, information disclosure, or a system crash. The function reads `dev->driver` twice without holding `device_lock()`, enabling a concurrent device unbind operation to clear the pointer between the NULL check and its subsequent dereference, resulting in use of a stale or NULL pointer in kernel context. No active exploitation has been identified (no CISA KEV listing, EPSS 0.18%), but the kernel-level impact class warrants prompt patching on affected stable branches.
The BPF signed loader in the Linux kernel fails to enforce map exclusivity before performing SHA-based integrity validation of metadata maps, allowing a local attacker with BPF privileges to race a mutation of the shared map's contents after the hash is computed but before validation completes. Systems running Linux kernel between commit fb2b0e290147ba01a53dfd92cf91058c9d2ee254 and the patched stable releases (6.18.40, 7.1.5, 7.2) are affected. Exploitation bypasses the integrity guarantees of the signed BPF loader, enabling the attacker to make the check pass on stale, attacker-controlled data; no public exploit exists and EPSS is 0.17% (6th percentile), indicating low current exploitation probability.
Out-of-bounds kernel memory reads in the Linux kernel's NTFS driver arise because ntfs_read_locked_inode() copies a resident $ATTRIBUTE_LIST into ni->attr_list via a plain memcpy() with no sanity checking, while only the non-resident path was ever validated by load_attribute_list(). A crafted NTFS volume with a malformed resident attribute list is then trusted by every subsequent walk (ntfs_external_attr_find(), ntfs_inode_attach_all_extents(), ntfs_attrlist_need()), which read fixed-header fields past the buffer. The fix factors per-entry validation into ntfs_attr_list_entry_is_valid()/ntfs_attr_list_is_valid() and applies it on the resident path and inside load_attribute_list() itself; no public exploit identified at time of analysis and EPSS probability is very low (0.15%).
Out-of-bounds slab read in the Linux kernel's legacy in-kernel NTFS driver lets a crafted on-disk $ATTRIBUTE_LIST leak or crash adjacent kernel heap memory when a malicious NTFS volume is mounted and read. The flaw is in ntfs_external_attr_find(), where a look-ahead attribute-list entry is dereferenced past the end of the kvmalloc'd buffer. There is no public exploit identified at time of analysis, EPSS risk is low (0.15%, 5th percentile), and it is not listed in CISA KEV.
Out-of-bounds kernel heap read in the Linux kernel's classic in-tree NTFS driver (`fs/ntfs/`) allows a local, low-privileged user to disclose kernel memory - and potentially chain to privilege escalation - by mounting a crafted NTFS image at the filesystem layer. The flaw is a u16 integer truncation in `ntfs_check_restart_area()` that silently defeats a page-size bounds check, causing `ntfs_check_log_client_array()` to dereference up to ~64 KiB beyond an allocated heap buffer using attacker-controlled on-disk values. No public exploit code exists and no active exploitation has been confirmed; EPSS is 0.15% (5th percentile), reflecting negligible observed exploitation pressure.
Heap and integer-overflow memory corruption in the Linux kernel's userspace perf tool (perf sched) lets a malicious perf.data file corrupt memory when parsed by register_pid(). An analyst who runs 'perf sched' against an attacker-supplied perf.data trace can trigger out-of-bounds heap writes, an unchecked strcpy into a 20-byte comm buffer, and denial of service, potentially leading to code execution in the context of the user running perf. A vendor fix is available; EPSS is low (0.18%) and there is no public exploit identified at time of analysis.
Out-of-bounds heap read in the Linux kernel's perf userspace tooling (perf tools) lets a crafted perf.data file trigger memory disclosure or a crash when parsed. The flaw sits in machine__resolve(), which trusts an attacker-controlled CPU index (al->cpu) from sample data and indexes env->cpu[] without validating it against env->nr_cpus_avail; a large index reads past the heap allocation, and values like 65536 truncate to int16_t and silently resolve to CPU 0. No public exploit is identified at time of analysis, and EPSS is low (0.18%, 7th percentile).
Use-after-free / stale-pointer race in the Linux kernel netfilter nf_conntrack_expect subsystem was resolved by replacing the per-expectation timer API with the conntrack garbage-collection worker. Under the old timer scheme, expectation removal could lose a race with an expiring timer (timer_del() returning false), leaving an expectation referencing an already-released exp->master conntrack, enabling stale-pointer access. The issue affects systems using connection-tracking helpers/expectations (e.g. FTP, SIP, or nft_ct expectations); no public exploit identified at time of analysis and it is not listed in CISA KEV, with a very low EPSS of 0.15% (5th percentile).
Availability denial in the Linux kernel's KVM ARM64 nested virtualization stack allows a guest VM to crash the host through improper Synchronous External Abort (SEA) handling when Stage 1 translation resolves a Guest Frame Number outside configured memory slots. Affected systems must run a vulnerable Linux 6.16-era kernel on ARM64 hardware with KVM nested virtualization explicitly enabled; fixed versions are 6.18.40, 7.1.5, and 7.2. No public exploit exists and no active exploitation is confirmed; EPSS stands at 0.18% (7th percentile), reflecting the niche attack surface.
NULL pointer dereference in the Linux kernel netfilter subsystem's xt_nat module allows a local attacker with low privileges to crash the kernel by instantiating SNAT or DNAT targets through the nft_compat compatibility layer using an unsupported bridge family, triggering a NULL dereference in nf_nat_setup_info(). Multiple stable kernel branches from 5.10 through 7.x are affected across numerous long-term support trees. No public exploit has been identified at time of analysis, and EPSS probability is very low at 0.18% (7th percentile); critically, the description itself notes the original crash was already mitigated by a prior upstream commit, making this patch a defense-in-depth hardening measure rather than a primary fix.
Symlink-based file clobbering in the Linux kernel's intel-speed-select daemon allows a local low-privileged user to redirect root-process writes to an attacker-chosen file by pre-positioning a symlink at the daemon's fixed /tmp pidfile path. Affected systems are those running Linux 5.18 through unpatched 6.x and 7.x branches on Intel Speed Select Technology hardware with the daemon active. No public exploit is identified at time of analysis and EPSS is low (0.17%, 7th percentile), but the attack is mechanically simple and requires only a local shell account.
Kernel stack disclosure and potential denial-of-service affect Linux systems with CXL hardware due to an off-by-8 size constant in the CXL RAS capability subsystem introduced in Linux 6.2. A local user who can trigger a CXL AER uncorrectable error and read tracefs can obtain up to 448 bytes of adjacent kernel stack data - potentially including code pointers and sensitive in-flight values - from the tracefs ring buffer. No public exploit identified at time of analysis; EPSS at 0.17% (6th percentile) reflects the niche CXL hardware dependency and local-only attack vector.
Use-after-free in the Linux kernel's UFS (Universal Flash Storage) core tracing subsystem allows a local attacker with tracing access to trigger a kernel crash or potentially achieve privilege escalation. The UFS trace event infrastructure stores raw pointers to the `hba` (Host Bus Adapter) structure in the trace ring buffer, then dereferences those pointers inside `TP_printk()` when `/sys/kernel/tracing/trace` is read - which may occur long after the underlying UFS device has been detached and its memory freed. No public exploit has been identified at time of analysis, and EPSS is 0.17% (6th percentile), indicating low near-term exploitation probability despite the high CVSS score.
Uninitialized-value access in the Linux kernel's HFS+ filesystem driver allows a local attacker with mount privileges to trigger kernel memory corruption or information disclosure by supplying a crafted disk image containing an invalid btree node_size. The flaw is reached during the mount path - specifically in hfsplus_bnode_find() while loading the HFS+ catalog B-tree - when a corrupted node_size value (e.g., 1) causes an excessively large offset to be passed to hfs_bnode_read_u16(), resulting in use of uninitialized stack memory. No public exploit has been identified and EPSS is 0.15% (5th percentile); upstream stable patches are available at git.kernel.org.
Race condition in the Linux kernel's hisi_sas v3 hardware driver triggers a kernel WARNING and potential memory corruption when SAS phy link reset and driver removal (rmmod) execute simultaneously. Specifically, during SAS phy bring-up, device_links_driver_bound sets the link status to DL_STATE_AVAILABLE, and a concurrent rmmod then causes __device_links_no_driver() to encounter an inconsistent device-link state. No public exploit exists and EPSS sits at 0.17% (6th percentile), reflecting this is a hardware-specific, privilege-intensive, timing-dependent flaw with very low exploitation likelihood in practice.
Out-of-bounds memory access in the Linux kernel's ARM SCMI firmware subsystem allows a local low-privileged attacker on ARM-based hardware to trigger kernel memory corruption via the scmi_power_name_get() function, which fails to validate the domain number supplied by external callers. Affected kernel versions span from the introduction commit 76a6550990e2 through multiple stable branches, with patches backported to LTS lines 5.15, 6.1, 6.6, 6.12, and 6.18. No public exploit code has been identified at time of analysis, and EPSS probability is very low at 0.17% (7th percentile), indicating no current attacker tooling interest despite the 7.8 CVSS score.
NULL pointer dereference in the Linux kernel IPv6 subsystem - specifically in `__in6_dev_stats_get()` - can crash the kernel and cause a denial of service when a physical network device is unregistered while IPv6 statistics are being collected. The vulnerability affects a wide range of stable kernel branches, from 4.19 through 7.x, and has been patched across all active LTS trees. No active exploitation is confirmed (not in CISA KEV) and EPSS at 0.18% (7th percentile) reflects low current real-world exploitation interest, though the ubiquitous deployment of the Linux kernel makes patch cadence important.
Invalid pointer dereference in the Linux kernel's RapidIO TSI721 driver allows an unauthenticated attacker on an adjacent RapidIO network to crash the kernel or corrupt memory by sending a crafted doorbell message. The root cause is a logic error in tsi721_db_dpc(): the 'found' flag is not reset at the start of each list_for_each() iteration, causing every doorbell after the first match to be treated as found, and causing list-end traversal with an invalid iterator pointer when no match exists. No public exploit exists and EPSS is 0.18% (7th percentile), consistent with the highly constrained physical attack surface; patches are available across multiple stable kernel branches.
Out-of-bounds write in the Linux kernel's OCFS2 cluster filesystem driver corrupts adjacent kernel memory when a low-privileged user unlinks a refcounted file whose refcount tree contains leaf blocks, triggering a fortify panic on hardened kernels. The root cause is an incorrect memset bound in `ocfs2_remove_refcount_extent()` arising from a union aliasing issue between `rf_records.rl_count` and `rf_list.l_tree_depth`. No public exploit or active exploitation has been identified; EPSS is 0.15% (5th percentile) and the vulnerability does not appear in CISA KEV, reflecting low real-world exploitation risk at time of analysis.
Unaligned memory access in the Linux kernel netfilter synproxy timestamp adjustment code can crash the kernel or degrade performance on strict-alignment CPU architectures when synproxy is actively configured. Systems running synproxy as a SYN-flood mitigation layer on architectures such as SPARC, classic MIPS, or ARM without hardware unaligned-access emulation are exposed to remote-triggered denial of service via crafted TCP packets. No active exploitation is confirmed (absent from CISA KEV) and EPSS at 0.17% (6th percentile) indicates negligible observed exploitation probability, though the network-reachable vector warrants timely patching on vulnerable platforms.
Out-of-bounds heap read in the Linux kernel's wcn36xx WiFi driver allows an adjacent-network attacker to corrupt Block Acknowledgment session state by sending crafted 802.11 frames that elicit a short firmware response. Kernels from 4.7 through pre-patch stable branches on devices equipped with Qualcomm WCN3660/WCN3620/WCN3680 WiFi hardware are affected. No public exploit code exists and no CISA KEV listing is present; EPSS of 0.17% (7th percentile) reflects negligible observed exploitation probability consistent with the hardware-specific attack surface.
Out-of-bounds stack read in the Linux kernel's netfilter flowtable (nf_flow_table / nft_dev_forward_path) affects the bridge VLAN-untag fast path, where a u8 num_encaps counter can underflow from 0 to 255 and cause the kernel to walk a fixed 2-entry encap[] array far past its bounds. Affected are kernels from 5.13 onward that use netfilter flowtable offload over bridge devices; the flaw leaks adjacent kernel stack memory into a route descriptor and copies a bogus encap count. No public exploit is identified at time of analysis, EPSS is low (0.15%), and it is not in CISA KEV.
Missing dma_resv lock acquisition before dma_buf_unpin() in the Linux kernel iommufd subsystem causes a kernel WARN on every IOAS destruction or unmap path that releases the last reference to a DMABUF-backed iopt_pages object. Affected are kernel versions from the commit introducing DMABUF pinning in iommufd (8c5f9645c389) through the fix commits in the 7.1 and 7.2 stable trees, with patches confirmed at Linux 7.1.5 and 7.2. No public exploit or active exploitation has been identified; EPSS is 0.15% (5th percentile), indicating negligible automated exploitation probability at time of analysis.
Null-pointer dereference in the Linux kernel's btrfs LZO decompression path can crash the kernel when reading a crafted compressed extent, causing a denial-of-service. Kernels in the range starting at commit a6e66e6f8c1b685e11b778bef614480a9c1a5278 through the two fix commits are affected across multiple stable branches (5.15 and later). No public exploit code or CISA KEV listing exists at time of analysis; the EPSS score of 0.15% (5th percentile) confirms this is not yet being exploited at scale. Exploitation requires the attacker to introduce a malformed btrfs filesystem image with LZO-compressed extents that the kernel then reads.
Memory corruption in the Linux kernel's net/sched fq_codel queueing discipline lets a local actor with traffic-control privileges trigger a wild kernel memory access and crash. When fq_codel drops packets during a peek operation, it calls qdisc_tree_reduce_backlog before restoring qlen; if qlen momentarily hits zero while peek still holds an skb, the parent class (e.g. qfq) is wrongly deactivated, producing a general-protection fault against a poisoned list pointer (0xdead000000000100 range) as seen under KASAN. No public exploit identified at time of analysis, EPSS is low (0.18%), and it is not in CISA KEV.
Race condition in the Linux kernel's ALSA OSS sequencer layer exposes local low-privilege attackers to kernel ring-buffer state corruption via unsynchronized reset operations. Specifically, snd_seq_oss_readq_clear() modifies qlen, head, and tail fields without holding q->lock, racing against reader and producer paths that correctly acquire the spinlock, potentially leaving stale or dropped MIDI events and corrupted readiness state. No public exploit identified at time of analysis; EPSS at 0.17% (6th percentile) indicates negligible current exploitation interest despite the CVSS 7.8 score reflecting theoretical kernel memory corruption severity.
Use-after-free and race condition vulnerabilities in the Linux kernel's tlclk (Telecom Clock) character driver expose local low-privileged users to potential kernel-space memory corruption, privilege escalation, or system crash. The module cleanup function tlclk_cleanup() frees alarm_events memory before awakening blocked waitqueue readers and before the switchover_timer completes, creating a use-after-free window during concurrent module unload. Additionally, the missing .owner field in file_operations allowed module unloading while userspace held the device open. No public exploit exists and EPSS is 0.18%, but patched kernel versions are confirmed across all active stable branches.
Use-after-free in the Linux kernel AppArmor subsystem's aa_replace_profiles function exposes kernelspace memory to corruption by a local low-privileged attacker. The defect arises from reading udata->size after aa_put_loaddata(udata) has released the reference - if that release triggers a free, the subsequent read constitutes a UAF that can be leveraged for privilege escalation or arbitrary kernel memory manipulation. EPSS sits at 0.18% (7th percentile) and no CISA KEV listing exists, indicating no confirmed widespread exploitation, though the local-access, low-complexity nature makes this a realistic intrahost threat on AppArmor-enabled systems.
Heap buffer overflow in the Linux kernel's Airoha (airoha_eth) network driver allows the packet-processing engine (PPE) flow-offload logic to write past an undersized allocation, corrupting kernel heap memory and crashing affected systems. The bug affects Linux 6.18.x through 6.18.39 and 6.19/7.x pre-release trees on hardware using the Airoha PPE flow-offload driver, and is triggered when airoha_ppe_foe_verify_entry() processes a flow hash at or above half the entry count. It is not in CISA KEV and has a low EPSS (0.18%), with no public exploit identified at time of analysis; impact is primarily denial of service.