Threats Tagged 'cve-2026-23199'

The SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues: The following security issues were fixed: - CVE-2025-68214: timers: Fix NULL function pointer race in timer_shutdown_sync() (bsc#1255225). - CVE-2025-68358: btrfs: fix racy bitfield write in btrfs_clear_space_info_full() (bsc#1255531). - CVE-2025-68780: sched/deadline: only set free_cpus for online runqueues (bsc#1256671). - CVE-2025-71075: scsi: aic94xx: fix use-after-free in device removal path (bsc#1256629). - CVE-2026-23113: io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop (bsc#1258278). - CVE-2026-23306: scsi: pm8001: Fix use-after-free in pm8001_queue_command() (bsc#1260501). - CVE-2026-23348: cxl/mem: Clarify @host for devm_cxl_add_nvdimm() (bsc#1260577). - CVE-2026-31418: netfilter: ipset: drop logically empty buckets in mtype_del (bsc#1262073). - CVE-2026-31530: cxl/port: Fix use after free of parent_port in cxl_detach_ep() (bsc#1262756). - CVE-2026-31531: ipv4: nexthop: allocate skb dynamically in rtm_get_nexthop() (bsc#1263004). - CVE-2026-43116: netfilter: ctnetlink: ensure safe access to master conntrack (bsc#1264619). - CVE-2026-43125: dlm: validate length in dlm_search_rsb_tree (bsc#1264541). - CVE-2026-43163: md/bitmap: fix GPF in write_page caused by resize race (bsc#1264335). - CVE-2026-43239: smb: client: prevent races in ->query_interfaces() (bsc#1264444). - CVE-2026-43271: md-cluster: fix NULL pointer dereference in process_metadata_update (bsc#1264587). - CVE-2026-43299: btrfs: do not ASSERT() when the fs flips RO inside btrfs_repair_io_failure() (bsc#1264851). - CVE-2026-43331: x86/kexec: Disable KCOV instrumentation after load_segments() (bsc#1265132). - CVE-2026-43355: iio: light: bh1780: fix PM runtime leak on error path (bsc#1265036). - CVE-2026-43363: x86/apic: Disable x2apic on resume if the kernel expects so (bsc#1265068). - CVE-2026-43416: powerpc, perf: Check that current->mm is alive before getting user callchain (bsc#1265121). - CVE-2026-43439: cgroup: fix race between task migration and iteration (bsc#1265141). - CVE-2026-43448: nvme-pci: Fix race bug in nvme_poll_irqdisable() (bsc#1264807). - CVE-2026-45860: netfilter: nf_conncount: increase the connection clean up limit to 64 (bsc#1266710). - CVE-2026-45897: netfilter: nft_counter: serialize reset with spinlock (bsc#1266897). - CVE-2026-45968: cpuidle: Skip governor when only one idle state is available (bsc#1267023). - CVE-2026-46007: hwmon: (powerz) Avoid cacheline sharing for DMA buffer (bsc#1267586). - CVE-2026-46070: md/raid5: validate payload size before accessing journal metadata (bsc#1267501). - CVE-2026-46107: dm-thin: fix metadata refcount underflow (bsc#1267612). - CVE-2026-46115: block: add pgmap check to biovec_phys_mergeable (bsc#1266874). - CVE-2026-46133: RDMA/rxe: Reject unknown opcodes before ICRC processing (bsc#1266928). - CVE-2026-46135: nvmet-tcp: remove redundant calls to nvmet_tcp_fatal_error() (bsc#1267373). - CVE-2026-46195: smb: client: validate dacloffset before building DACL pointers (bsc#1266860). - CVE-2026-46304: nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free (bsc#1267985). - CVE-2026-52912: netfilter: nf_queue: hold bridge skb->dev while queued (bsc#1269000). - CVE-2026-52920: netfilter: xt_policy: fix strict mode inbound policy matching (bsc#1269013). - CVE-2026-52928: af_unix: Reject SIOCATMARK on non-stream sockets (bsc#1269010). - CVE-2026-52929: sctp: stream: fully roll back denied add-stream state (bsc#1269004). - CVE-2026-52935: xfrm: espintcp: do not reuse an in-progress partial send (bsc#1268979). - CVE-2026-52939: net/rds: fix NULL deref in rds_ib_send_cqe_handler() on masked atomic completion (bsc#1268972). - CVE-2026-52946: fs/fcntl: fix SOFTIRQ-unsafe lock order in fasync signaling (bsc#1269113). - CVE-2026-52977: futex: Prevent lockup in requeue-PI during signal/ timeout wakeup (bsc#1269242). - CVE-2026-52990: fsnotify: fix inode reference leak in fsnotify_recalc_mask() (bsc#1269108). - CVE-2026-52991: sched/psi: fix race between file release and pressure write (bsc#1269134). - CVE-2026-52994: vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting (bsc#1269126). - CVE-2026-53001: netfilter: xtables: restrict several matches to inet family (bsc#1269114). - CVE-2026-53031: bpf: Validate node_id in arena_alloc_pages() (bsc#1269380). - CVE-2026-53033: bpf, sockmap: Take state lock for af_unix iter (bsc#1269388). - CVE-2026-53034: bpf, sockmap: Fix af_unix null-ptr-deref in proto update (bsc#1269140). - CVE-2026-53048: gfs2: prevent NULL pointer dereference during unmount (bsc#1269162). - CVE-2026-53059: dm log: fix out-of-bounds write due to region_count overflow (bsc#1269655). - CVE-2026-53061: dm cache: fix dirty mapping checking in passthrough mode switching (bsc#1269685). - CVE-2026-53076: bpf: Fix OOB in pcpu_init_value (bsc#1269695). - CVE-2026-53077: net/rds: Restrict use of RDS/IB to the initial network namespace (bsc#1269412). - CVE-2026-53089: bpf: Fix use-after-free

In the Linux kernel, the following vulnerability has been resolved: procfs: avoid fetching build ID while holding VMA lock Fix PROCMAP_QUERY to fetch optional build ID only after dropping mmap_lock or per-VMA lock, whichever was used to lock VMA under question, to avoid deadlock reported by syzbot: -> #1 (&mm->mmap_lock){++++}-{4:4}: __might_fault+0xed/0x170 _copy_to_iter+0x118/0x1720 copy_page_to_iter+0x12d/0x1e0 filemap_read+0x720/0x10a0 blkdev_read_iter+0x2b5/0x4e0 vfs_read+0x7f4/0xae0 ksys_read+0x12a/0x250 do_syscall_64+0xcb/0xf80 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&sb->s_type->i_mutex_key#8){++++}-{4:4}: __lock_acquire+0x1509/0x26d0 lock_acquire+0x185/0x340 down_read+0x98/0x490 blkdev_read_iter+0x2a7/0x4e0 __kernel_read+0x39a/0xa90 freader_fetch+0x1d5/0xa80 __build_id_parse.isra.0+0xea/0x6a0 do_procmap_query+0xd75/0x1050 procfs_procmap_ioctl+0x7a/0xb0 __x64_sys_ioctl+0x18e/0x210 do_syscall_64+0xcb/0xf80 entry_SYSCALL_64_after_hwframe+0x77/0x7f other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- rlock(&mm->mmap_lock); lock(&sb->s_type->i_mutex_key#8); lock(&mm->mmap_lock); rlock(&sb->s_type->i_mutex_key#8); *** DEADLOCK *** This seems to be exacerbated (as we haven't seen these syzbot reports before that) by the recent: 777a8560fd29 ("lib/buildid: use __kernel_read() for sleepable context") To make this safe, we need to grab file refcount while VMA is still locked, but other than that everything is pretty straightforward. Internal build_id_parse() API assumes VMA is passed, but it only needs the underlying file reference, so just add another variant build_id_parse_file() that expects file passed directly. [[email protected]: fix up kerneldoc]