CVE-2026-98380

net/sched: reject IDR error pointers when deleting actions

State
Published
Severity
Not scored
Published
Oct 9, 2026
Updated
Oct 19, 2026
Reserved
Sep 25, 2026

Read the record on cve.org

Description

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

net/sched: reject IDR error pointers when deleting actions

tcf_action_delete() drops the reference held by its lookup before calling tcf_idr_delete_index() with the saved action index. An unlocked classifier can remove that action and reserve the same IDR slot with ERR_PTR(-EBUSY) in between.

tcf_idr_delete_index() only checks the lookup result for NULL. It therefore treats the reservation as a tc_action and dereferences tcfa_bindcnt. A hardware execution breakpoint was used to schedule the interleaving without changing the kernel source. KASAN reported this decoded trace:

BUG: KASAN: null-ptr-deref in tca_action_gd+0x5b9/0x1010 Read of size 4 at addr 0000000000000010 by task poc/150 Oops: general protection fault, probably for non-canonical address 0xdffffc0000000002 RIP: tca_action_gd+0x5c0/0x1010: arch_atomic_read at arch/x86/include/asm/atomic.h:23 raw_atomic_read at include/linux/atomic/atomic-arch-fallback.h:457 atomic_read at include/linux/atomic/atomic-instrumented.h:33 tcf_idr_delete_index at net/sched/act_api.c:766 tcf_action_delete at net/sched/act_api.c:1859 tcf_del_notify at net/sched/act_api.c:2014 tca_action_gd at net/sched/act_api.c:2064 R13: 0000000000000010 R15: fffffffffffffff0 Kernel panic - not syncing: Fatal exception

R15 contains ERR_PTR(-EBUSY), and adding the tcfa_bindcnt offset produces the address in R13. With the guard applied, the same reproducer returned -ENOENT without a KASAN report or panic. Treat error pointers as absent and return -ENOENT.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 0190c1d452a91c38a3462abdd81752be1b9006a8 to before 39b751a210bf61a374afa82749afc7a77a08bf1dAffected
  • 0190c1d452a91c38a3462abdd81752be1b9006a8 to before dd80a7519824b72c8fcfd3cc50cb93f7e2d90923Affected
  • 0190c1d452a91c38a3462abdd81752be1b9006a8 to before 6bf076258aac4e0af69ef317656c31ce6444d647Affected
  • 0190c1d452a91c38a3462abdd81752be1b9006a8 to before 6c9f07bf8800171de2cd3f02815cebe1f4d45f2dAffected
  • 0190c1d452a91c38a3462abdd81752be1b9006a8 to before 259caa711b7688365676442e2fdb286b8aceaa80Affected
  • 0190c1d452a91c38a3462abdd81752be1b9006a8 to before 968550a439f64bd1a6c0d88efb92e4f082f84a26Affected
  • 0190c1d452a91c38a3462abdd81752be1b9006a8 to before a9551f26287debe6d8aa6e8841974661065b975fAffected
  • 0190c1d452a91c38a3462abdd81752be1b9006a8 to before c82b797abe668d0b668601a93ba2c0b071a63574Affected
LinuxLinux
  • 4.19Affected
  • before 4.19Not affected
  • 5.10.271 through 5.10.*Not affected
  • 5.15.222 through 5.15.*Not affected
  • 6.1.189 through 6.1.*Not affected
  • 6.6.158 through 6.6.*Not affected
  • 6.12.112 through 6.12.*Not affected
  • 6.18.55 through 6.18.*Not affected
  • 7.2.9 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.