CVE-2026-23371

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:

f2fs: fix to detect potential corrupted nid in free_nid_list

As reported, on-disk footer.ino and footer.nid is the same and out-of-range, let's add sanity check on f2fs_alloc_nid() to detect any potential corruption in free_nid_list.(CVE-2025-68315)

In the Linux kernel, the following vulnerability has been resolved:

ntfs3: Fix uninit buffer allocated by __getname()

Fix uninit errors caused after buffer allocation given to 'de'; by initializing the buffer with zeroes. The fix was found by using KMSAN.(CVE-2025-68727)

In the Linux kernel, the following vulnerability has been resolved:

netfilter: nf_tables: fix use-after-free in nf_tables_addchain()

nf_tables_addchain() publishes the chain to table->chains via list_add_tail_rcu() (in nft_chain_add()) before registering hooks. If nf_tables_register_hook() then fails, the error path calls nft_chain_del() (list_del_rcu()) followed by nf_tables_chain_destroy() with no RCU grace period in between.

This creates two use-after-free conditions:

1. Control-plane: nf_tables_dump_chains() traverses table->chains under rcu_read_lock(). A concurrent dump can still be walking the chain when the error path frees it.

2. Packet path: for NFPROTO_INET, nf_register_net_hook() briefly installs the IPv4 hook before IPv6 registration fails. Packets entering nft_do_chain() via the transient IPv4 hook can still be dereferencing chain->blob_gen_X when the error path frees the chain.

Add synchronize_rcu() between nft_chain_del() and the chain destroy so that all RCU readers -- both dump threads and in-flight packet evaluation -- have finished before the chain is freed.(CVE-2026-23231)

In the Linux kernel, the following vulnerability has been resolved:

tls: Fix race condition in tls_sw_cancel_work_tx()

This issue was discovered during a code audit.

After cancel_delayed_work_sync() is called from tls_sk_proto_close(), tx_work_handler() can still be scheduled from paths such as the Delayed ACK handler or ksoftirqd. As a result, the tx_work_handler() worker may dereference a freed TLS object.

The following is a simple race scenario:

      cpu0                         cpu1

tls_sk_proto_close() tls_sw_cancel_work_tx() tls_write_space() tls_sw_write_space() if (!test_and_set_bit(BIT_TX_SCHEDULED, &tx_ctx->tx_bitmask)) set_bit(BIT_TX_SCHEDULED, &ctx->tx_bitmask); cancel_delayed_work_sync(&ctx->tx_work.work); schedule_delayed_work(&tx_ctx->tx_work.work, 0);

To prevent this race condition, cancel_delayed_work_sync() is replaced with disable_delayed_work_sync().(CVE-2026-23240)

In the Linux kernel, the following vulnerability has been resolved:

net/sched: act_gate: snapshot parameters with RCU on replace

The gate action can be replaced while the hrtimer callback or dump path is walking the schedule list.

Convert the parameters to an RCU-protected snapshot and swap updates under tcf_lock, freeing the previous snapshot via call_rcu(). When REPLACE omits the entry list, preserve the existing schedule so the effective state is unchanged.(CVE-2026-23245)

In the Linux kernel, the following vulnerability has been resolved:

net: gro: fix outer network offset

The udp GRO complete stage assumes that all the packets inserted the RX have the encapsulation flag zeroed. Such assumption is not true, as a few H/W NICs can set such flag when H/W offloading the checksum for an UDP encapsulated traffic, the tun driver can inject GSO packets with UDP encapsulation and the problematic layout can also be created via a veth based setup.

Due to the above, in the problematic scenarios, udp4_gro_complete() uses the wrong network offset (inner…

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:

f2fs: fix to detect potential corrupted nid in free_nid_list

As reported, on-disk footer.ino and footer.nid is the same and out-of-range, let's add sanity check on f2fs_alloc_nid() to detect any potential corruption in free_nid_list.(CVE-2025-68315)

In the Linux kernel, the following vulnerability has been resolved:

ntfs3: Fix uninit buffer allocated by __getname()

Fix uninit errors caused after buffer allocation given to 'de'; by initializing the buffer with zeroes. The fix was found by using KMSAN.(CVE-2025-68727)

In the Linux kernel, a security vulnerability exists in the IOMMU Shared Virtual Addressing (SVA) feature. On x86 architecture when CONFIG_X86 is set, IOMMU hardware caches kernel page table entries. Due to the lack of notification mechanism for kernel page table changes, when kernel page table pages are freed and reused, the IOMMU may retain stale entries, leading to Use-After-Free (UAF) and Write-After-Free (WAF) conditions. This can be exploited to cause arbitrary physical memory DMA access or privilege escalation.(CVE-2025-71089)

In the Linux kernel, the following vulnerability has been resolved:

uacce: fix cdev handling in the cleanup path

When cdev_device_add fails, it internally releases the cdev memory, and if cdev_device_del is then executed, it will cause a hang error. To fix it, we check the return value of cdev_device_add() and clear uacce->cdev to avoid calling cdev_device_del in the uacce_remove.(CVE-2026-23096)

In the Linux kernel, the following vulnerability has been resolved:

bonding: fix use-after-free due to enslave fail after slave array update

Fix a use-after-free which happens due to enslave failure after the new slave has been added to the array. Since the new slave can be used for Tx immediately, we can use it after it has been freed by the enslave error cleanup path which frees the allocated slave memory. Slave update array is supposed to be called last when further enslave failures are not expected. Move it after xdp setup to avoid any problems.

It is very easy to reproduce the problem with a simple xdp_pass prog: ip l add bond1 type bond mode balance-xor ip l set bond1 up ip l set dev bond1 xdp object xdp_pass.o sec xdp_pass ip l add dumdum type dummy

Then run in parallel: while :; do ip l set dumdum master bond1 1>/dev/null 2>&1; done; mausezahn bond1 -a own -b rand -A rand -B 1.1.1.1 -c 0 -t tcp "dp=1-1023, flags=syn"

The crash happens almost immediately: [ 605.602850] Oops: general protection fault, probably for non-canonical address 0xe0e6fc2460000137: 0000 [#1] SMP KASAN NOPTI [ 605.602916] KASAN: maybe wild-memory-access in range [0x07380123000009b8-0x07380123000009bf] [ 605.602946] CPU: 0 UID: 0 PID: 2445 Comm: mausezahn Kdump: loaded Tainted: G B 6.19.0-rc6+ #21 PREEMPT(voluntary) [ 605.602979] Tainted: [B]=BAD_PAGE [ 605.602998] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 605.603032] RIP: 0010:netdev_core_pick_tx+0xcd/0x210 [ 605.603063] Code: 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 3e 01 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8b 6b 08 49 8d 7d 30 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 25 01 00 00 49 8b 45 30 4c 89 e2 48 89 ee 48 89 [ 605.603111] RSP: 0018:ffff88817b9af348 EFLAGS: 00010213 [ 605.603145] RAX: dffffc0000000000 RBX: ffff88817d28b420 RCX: 0000000000000000 [ 605.603172] RDX: 00e7002460000137 RSI: 0000000000000008 RDI: 07380123000009be [ 605.603199] RBP: ffff88817b541a00 R08: 0000000000000001 R09: fffffbfff3ed8c0c [ 605.603226] R10: ffffffff9f6c6067 R11: 0000000000000001 R12: 0000000000000000 [ 605.603253] R13: 073801230000098e R14: ffff88817d28b448 R15: ffff88817b541a84 [ 605.603286] FS: 00007f6570ef67c0(0000) GS:ffff888221dfa000(0000) knlGS:0000000000000000 [ …

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:

f2fs: fix to detect potential corrupted nid in free_nid_list

As reported, on-disk footer.ino and footer.nid is the same and out-of-range, let's add sanity check on f2fs_alloc_nid() to detect any potential corruption in free_nid_list.(CVE-2025-68315)

In the Linux kernel, the following vulnerability has been resolved:

ntfs3: Fix uninit buffer allocated by __getname()

Fix uninit errors caused after buffer allocation given to 'de'; by initializing the buffer with zeroes. The fix was found by using KMSAN.(CVE-2025-68727)

In the Linux kernel, the following vulnerability has been resolved:

netfilter: nf_tables: fix use-after-free in nf_tables_addchain()

nf_tables_addchain() publishes the chain to table->chains via list_add_tail_rcu() (in nft_chain_add()) before registering hooks. If nf_tables_register_hook() then fails, the error path calls nft_chain_del() (list_del_rcu()) followed by nf_tables_chain_destroy() with no RCU grace period in between.

This creates two use-after-free conditions:

1. Control-plane: nf_tables_dump_chains() traverses table->chains under rcu_read_lock(). A concurrent dump can still be walking the chain when the error path frees it.

2. Packet path: for NFPROTO_INET, nf_register_net_hook() briefly installs the IPv4 hook before IPv6 registration fails. Packets entering nft_do_chain() via the transient IPv4 hook can still be dereferencing chain->blob_gen_X when the error path frees the chain.

Add synchronize_rcu() between nft_chain_del() and the chain destroy so that all RCU readers -- both dump threads and in-flight packet evaluation -- have finished before the chain is freed.(CVE-2026-23231)

In the Linux kernel, the following vulnerability has been resolved:

tls: Fix race condition in tls_sw_cancel_work_tx()

This issue was discovered during a code audit.

After cancel_delayed_work_sync() is called from tls_sk_proto_close(), tx_work_handler() can still be scheduled from paths such as the Delayed ACK handler or ksoftirqd. As a result, the tx_work_handler() worker may dereference a freed TLS object.

The following is a simple race scenario:

      cpu0                         cpu1

tls_sk_proto_close() tls_sw_cancel_work_tx() tls_write_space() tls_sw_write_space() if (!test_and_set_bit(BIT_TX_SCHEDULED, &tx_ctx->tx_bitmask)) set_bit(BIT_TX_SCHEDULED, &ctx->tx_bitmask); cancel_delayed_work_sync(&ctx->tx_work.work); schedule_delayed_work(&tx_ctx->tx_work.work, 0);

To prevent this race condition, cancel_delayed_work_sync() is replaced with disable_delayed_work_sync().(CVE-2026-23240)

In the Linux kernel, the following vulnerability has been resolved:

net/sched: act_gate: snapshot parameters with RCU on replace

The gate action can be replaced while the hrtimer callback or dump path is walking the schedule list.

Convert the parameters to an RCU-protected snapshot and swap updates under tcf_lock, freeing the previous snapshot via call_rcu(). When REPLACE omits the entry list, preserve the existing schedule so the effective state is unchanged.(CVE-2026-23245)

In the Linux kernel, the following vulnerability has been resolved:

net: gro: fix outer network offset

The udp GRO complete stage assumes that all the packets inserted the RX have the encapsulation flag zeroed. Such assumption is not true, as a few H/W NICs can set such flag when H/W offloading the checksum for an UDP encapsulated traffic, the tun driver can inject GSO packets with UDP encapsulation and the problematic layout can also be created via a veth based setup.

Due to the above, in the problematic scenarios, udp4_gro_complete() uses the wrong network offset (inner…

Root has patched CVE-2026-23371 in the linux package for Root:Debian:11. Multiple fixed versions available.

Root has patched CVE-2026-23371 in the linux package for Root:Debian:12. Multiple fixed versions available.

Root has patched CVE-2026-23371 in the linux package for Root:Ubuntu:22.04. Multiple fixed versions available.

Root has patched CVE-2026-23371 in the linux package for Root:Ubuntu:24.04. Multiple fixed versions available.

In the Linux kernel, the following vulnerability has been resolved: sched/deadline: Fix missing ENQUEUE_REPLENISH during PI de-boosting Running stress-ng --schedpolicy 0 on an RT kernel on a big machine might lead to the following WARNINGs (edited). sched: DL de-boosted task PID 22725: REPLENISH flag missing WARNING: CPU: 93 PID: 0 at kernel/sched/deadline.c:239 dequeue_task_dl+0x15c/0x1f8 ... (running_bw underflow) Call trace: dequeue_task_dl+0x15c/0x1f8 (P) dequeue_task+0x80/0x168 deactivate_task+0x24/0x50 push_dl_task+0x264/0x2e0 dl_task_timer+0x1b0/0x228 __hrtimer_run_queues+0x188/0x378 hrtimer_interrupt+0xfc/0x260 ... The problem is that when a SCHED_DEADLINE task (lock holder) is changed to a lower priority class via sched_setscheduler(), it may fail to properly inherit the parameters of potential DEADLINE donors if it didn't already inherit them in the past (shorter deadline than donor's at that time). This might lead to bandwidth accounting corruption, as enqueue_task_dl() won't recognize the lock holder as boosted. The scenario occurs when: 1. A DEADLINE task (donor) blocks on a PI mutex held by another DEADLINE task (holder), but the holder doesn't inherit parameters (e.g., it already has a shorter deadline) 2. sched_setscheduler() changes the holder from DEADLINE to a lower class while still holding the mutex 3. The holder should now inherit DEADLINE parameters from the donor and be enqueued with ENQUEUE_REPLENISH, but this doesn't happen Fix the issue by introducing __setscheduler_dl_pi(), which detects when a DEADLINE (proper or boosted) task gets setscheduled to a lower priority class. In case, the function makes the task inherit DEADLINE parameters of the donoer (pi_se) and sets ENQUEUE_REPLENISH flag to ensure proper bandwidth accounting during the next enqueue operation.

In the Linux kernel, the following vulnerability has been resolved:

sched/deadline: Fix missing ENQUEUE_REPLENISH during PI de-boosting

Running stress-ng --schedpolicy 0 on an RT kernel on a big machine might lead to the following WARNINGs (edited).

sched: DL de-boosted task PID 22725: REPLENISH flag missing

WARNING: CPU: 93 PID: 0 at kernel/sched/deadline.c:239 dequeue_task_dl+0x15c/0x1f8 ... (running_bw underflow) Call trace: dequeue_task_dl+0x15c/0x1f8 (P) dequeue_task+0x80/0x168 deactivate_task+0x24/0x50 push_dl_task+0x264/0x2e0 dl_task_timer+0x1b0/0x228 __hrtimer_run_queues+0x188/0x378 hrtimer_interrupt+0xfc/0x260 ...

The problem is that when a SCHED_DEADLINE task (lock holder) is changed to a lower priority class via sched_setscheduler(), it may fail to properly inherit the parameters of potential DEADLINE donors if it didn't already inherit them in the past (shorter deadline than donor's at that time). This might lead to bandwidth accounting corruption, as enqueue_task_dl() won't recognize the lock holder as boosted.

The scenario occurs when:

1. A DEADLINE task (donor) blocks on a PI mutex held by another DEADLINE task (holder), but the holder doesn't inherit parameters (e.g., it already has a shorter deadline)
2. sched_setscheduler() changes the holder from DEADLINE to a lower class while still holding the mutex
3. The holder should now inherit DEADLINE parameters from the donor and be enqueued with ENQUEUE_REPLENISH, but this doesn't happen

Fix the issue by introducing __setscheduler_dl_pi(), which detects when a DEADLINE (proper or boosted) task gets setscheduled to a lower priority class. In case, the function makes the task inherit DEADLINE parameters of the donoer (pi_se) and sets ENQUEUE_REPLENISH flag to ensure proper bandwidth accounting during the next enqueue operation.

• wifi: ath11k: update channel list in reg notifier instead reg worker {CVE-2025-23133}
• wifi: cfg80211: call reg_notifier for self managed wiphy from driver hint {CVE-2025-23133}
• KVM: SVM: Forcibly leave SMM mode on SHUTDOWN interception {CVE-2025-37957}
• KVM: x86: forcibly leave nested mode on vCPU reset {CVE-2022-3344}
• RDMA/umem: Fix truncation for block sizes >= 4G {CVE-2026-53133}
• crypto: arm64/poly1305 - fix a read out-of-bound {CVE-2022-50231}
• tls: handle data disappearing from under the TLS ULP {CVE-2025-38616}
• Bluetooth: btmtk: validate WMT event SKB length before struct access {CVE-2026-46140}
• Bluetooth: L2CAP: complete CVE-2026-23395 hardening (chan_lock + ident clear + memset ordering)
• wireguard: device: use exit_rtnl callback instead of manual rtnl_lock in pre_exit {CVE-2026-31579}
• net: add exit_batch_rtnl() method
• rxrpc: Fix data-race warning and potential load/store tearing {CVE-2026-23118}
• virt/coco/sev-guest: Double-buffer messages {CVE-2023-53769}
• ASoC: SOF: avoid a NULL dereference with unsupported widgets {CVE-2023-54233}
• bnxt_en: Fix memory corruption when FW resources change during ifdown {CVE-2025-39810}
• scsi: qla2xxx: Free sp in error path to fix system crash {CVE-2025-71232}
• sched/deadline: Fix missing ENQUEUE_REPLENISH during PI de-boosting {CVE-2026-23371}
• net: rfkill: prevent unlimited numbers of rfkill events from being created {CVE-2026-31670}
• intel_th: fix device leak on output open() {CVE-2026-23091}
• batman-adv: reject oversized global TT response buffers {CVE-2026-31659}
• rxrpc: Fix call removal to use RCU safe deletion {CVE-2026-31642}
• i2c: s3c24xx: check the size of the SMBUS message before using it {CVE-2026-31627}
• Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop {CVE-2026-31498}
• mtd: rawnand: serialize lock/unlock against other NAND operations {CVE-2026-23434}
• x86/efi: defer freeing of boot services memory {CVE-2026-23352}
• KVM: Don't clobber irqfd routing type when deassigning irqfd {CVE-2026-23198}
• nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec {CVE-2026-23112}
• usb: typec: ucsi: Handle incorrect num_connectors capability {CVE-2025-71108}
• KVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer {CVE-2025-71104}
• drm/ttm: Avoid NULL pointer deref for evicted BOs {CVE-2025-71083}
• amba: bus: fix refcount leak {CVE-2023-54230}
• exfat: use kvmalloc_array/kvfree instead of kmalloc_array/kfree {CVE-2023-54194}
• octeontx2-af: Add validation for lmac type {CVE-2023-54129}
• rcu: dump vmalloc memory info safely {CVE-2023-54113}
• wifi: rtw88: use work to update rate to avoid RCU warning {CVE-2023-54071}
• bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps {CVE-2023-54033}
• ASoC: soc-compress: Reposition and add pcm_mutex {CVE-2023-53866}
• netlink: do not hard code device address lenth in fdb dumps {CVE-2023-53863}
• md/raid5-cache: fix a deadlock in r5l_exit_log() {CVE-2023-53848}
• tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak {CVE-2022-50824}
• net: stmmac: fix possible memory leak in stmmac_dvr_probe() {CVE-2022-50663}
• bpf: Fix reference state management for synchronous callbacks {CVE-2022-50650}
• blk-mq: fix tags leak when shrink nr_hw_queues {CVE-2023-54227}
• usbnet: Run unregister_netdev() before unbind() again {CVE-2022-49501}
• scsi: core: Wake up the error handler when final completions race against each other {CVE-2026-23110}
• scsi: core: Move scsi_host_busy() out of host lock for waking up EH handler
• perf/core: Prevent VMA split of buffer mappings {CVE-2025-38563}
• Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ {CVE-2026-23395}
• Bluetooth: L2CAP: Fix responding with wrong PDU type
• netfilter: nf_tables: release flowtable after rcu grace period on error {CVE-2026-23392}

• nvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers
• RDMA/mlx5: Fix unsafe xarray access in implicit ODP handling
• wifi: rtlwifi: pci: wait for firmware loading before releasing memory
• wifi: rtlwifi: fix memory leaks and invalid access at probe error path {CVE-2024-58063}
• tracing: Fix bad hist from corrupting named_triggers list {CVE-2025-21899}
• PM / devfreq: Fix leak in devfreq_dev_release() {CVE-2023-53518}
• net: usb: asix_devices: Fix PHY address mask in MDIO bus initialization {CVE-2025-38725}
• net/sched: Fix backlog accounting in qdisc_dequeue_internal {CVE-2025-37992}
• nfsd: decrease sc_count directly if fail to queue dl_recall {CVE-2025-22025}
• net: usb: asix_devices: add phy_mask for ax88772 mdio bus {CVE-2025-38725}
• nfsd: put dl_stid if fail to queue dl_recall {CVE-2025-22025}
• rtnetlink: add missing netlink_ns_capable() check for peer netns {CVE-2026-31692}
• mm: add smp_rmb() in pfn_swap_entry_to_page() to pair with THP split {CVE-2026-31466}
• net_sched: Flush gso_skb list too during ->change() {CVE-2025-37992}
• io_uring: fix use-after-free of sq->thread in __io_uring_show_fdinfo() {CVE-2025-38106}
• Input: cyapa - add missing input core locking to suspend/resume functions {CVE-2023-52884}
• mtd: rawnand: serialize lock/unlock against other NAND operations {CVE-2026-23434}
• be2net: fix potential memory leak in be_xmit() {CVE-2024-50167}
• net: stmmac: TSO: Fix unbalanced DMA map/unmap for non-paged SKB data {CVE-2024-53058}
• Drivers: hv: util: Avoid accessing a ringbuffer not initialized yet {CVE-2024-55916}
• idpf: detach and close netdevs while handling a reset {CVE-2026-22981}
• ice: fix devlink reload call trace {CVE-2026-23104}
• nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec {CVE-2026-23112}
• bpf: Prevent tailcall infinite loop caused by freplace {CVE-2024-47794}
• crypto: pcrypt - restore callback for non-parallel fallback
• crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY {CVE-2024-56690}
• tracing/histograms: Allow variables to have some modifiers {CVE-2023-53093}
• intel_th: fix device leak on output open() {CVE-2026-23091}
• RDMA/mlx5: Fix implicit ODP hang on parent deregistration
• RDMA/mlx5: Fix implicit ODP use after free {CVE-2025-21714}
• net: stmmac: make sure that ptp_rate is not 0 before configuring timestamping {CVE-2025-38126}
• KVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer {CVE-2025-71104}
• i2c: s3c24xx: check the size of the SMBUS message before using it {CVE-2026-31627}
• scsi: qla2xxx: Free sp in error path to fix system crash {CVE-2025-71232}
• nfc: llcp: add missing return after LLCP_CLOSED checks {CVE-2026-31629}
• gfs2: No more self recovery {CVE-2025-38659}
• hugetlbfs: fix null-ptr-deref in hugetlbfs_parse_param() {CVE-2022-50334}
• tracing: Prevent bad count for tracing_cpumask_write {CVE-2024-56763}
• CDC-NCM: avoid overflow in sanity checking {CVE-2022-48938}
• cxl: Fix race of nvdimm_bus object when creating nvdimm objects {CVE-2026-23348}
• KVM: SEV: Protect all of sev_mem_enc_register_region() with kvm->lock {CVE-2026-31592}
• sched/deadline: Fix missing ENQUEUE_REPLENISH during PI de-boosting {CVE-2026-23371}
• md/raid1,raid10: don't ignore IO flags {CVE-2025-22125}
• mm: slub: avoid wake up kswapd in set_track_prepare {CVE-2025-39843}
• iommu/vt-d: Disallow dirty tracking if incoherent page walk {CVE-2025-40058}
• backlight: led_bl: Hold led_access lock when calling led_sysfs_disable() {CVE-2025-23144}
• PCI: Avoid putting some root ports into D3 on TUXEDO Sirius Gen1 {CVE-2025-21831}
• drm/amd/display: Add null pointer check for get_first_active_display() {CVE-2025-38362}
• pinctrl: devicetree: fix refcount leak in pinctrl_dt_to_map()
• pinctrl: devicetree: fix null pointer dereferencing in pinctrl_dt_to_map {CVE-2022-49832}
• spi: fsl-qspi: Simplify probe error handling using managed API
• spi: fsl-qspi: Fix double cleanup in probe error path
• spi:…

In the Linux kernel, the following vulnerability has been resolved:

sched/deadline: Fix missing ENQUEUE_REPLENISH during PI de-boosting

Running stress-ng --schedpolicy 0 on an RT kernel on a big machine might lead to the following WARNINGs (edited).

sched: DL de-boosted task PID 22725: REPLENISH flag missing

WARNING: CPU: 93 PID: 0 at kernel/sched/deadline.c:239 dequeue_task_dl+0x15c/0x1f8 ... (running_bw underflow) Call trace: dequeue_task_dl+0x15c/0x1f8 (P) dequeue_task+0x80/0x168 deactivate_task+0x24/0x50 push_dl_task+0x264/0x2e0 dl_task_timer+0x1b0/0x228 __hrtimer_run_queues+0x188/0x378 hrtimer_interrupt+0xfc/0x260 ...

The problem is that when a SCHED_DEADLINE task (lock holder) is changed to a lower priority class via sched_setscheduler(), it may fail to properly inherit the parameters of potential DEADLINE donors if it didn't already inherit them in the past (shorter deadline than donor's at that time). This might lead to bandwidth accounting corruption, as enqueue_task_dl() won't recognize the lock holder as boosted.

The scenario occurs when:

1. A DEADLINE task (donor) blocks on a PI mutex held by another DEADLINE task (holder), but the holder doesn't inherit parameters (e.g., it already has a shorter deadline)
2. sched_setscheduler() changes the holder from DEADLINE to a lower class while still holding the mutex
3. The holder should now inherit DEADLINE parameters from the donor and be enqueued with ENQUEUE_REPLENISH, but this doesn't happen

Fix the issue by introducing __setscheduler_dl_pi(), which detects when a DEADLINE (proper or boosted) task gets setscheduled to a lower priority class. In case, the function makes the task inherit DEADLINE parameters of the donoer (pi_se) and sets ENQUEUE_REPLENISH flag to ensure proper bandwidth accounting during the next enqueue operation.