net/sched: reject IDR error pointers when deleting actions
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 0190c1d452a91c38a3462abdd81752be1b9006a8 · fixed in 39b751a210bf61a374afa82749afc7a77a08bf1d; From 0190c1d452a91c38a3462abdd81752be1b9006a8 · fixed in dd80a7519824b72c8fcfd3cc50cb93f7e2d90923; From 0190c1d452a91c38a3462abdd81752be1b9006a8 · fixed in 6bf076258aac4e0af69ef317656c31ce6444d647; From 0190c1d452a91c38a3462abdd81752be1b9006a8 · fixed in 6c9f07bf8800171de2cd3f02815cebe1f4d45f2d; From 0190c1d452a91c38a3462abdd81752be1b9006a8 · fixed in 259caa711b7688365676442e2fdb286b8aceaa80; From 0190c1d452a91c38a3462abdd81752be1b9006a8 · fixed in 968550a439f64bd1a6c0d88efb92e4f082f84a26; From 0190c1d452a91c38a3462abdd81752be1b9006a8 · fixed in a9551f26287debe6d8aa6e8841974661065b975f; From 0190c1d452a91c38a3462abdd81752be1b9006a8 · fixed in c82b797abe668d0b668601a93ba2c0b071a63574
- Linux Linux
4.19
- KernelLinux
From 4.19.0 · fixed in 5.10.271; From 5.11.0 · fixed in 5.15.222; From 5.16.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.55; From 6.19.0 · fixed in 7.2.9
References 8
git.kernel.org
- stable/c/39b751a210bf61a374afa82749afc7a77a08bf1d
- stable/c/dd80a7519824b72c8fcfd3cc50cb93f7e2d90923
- stable/c/6bf076258aac4e0af69ef317656c31ce6444d647
- stable/c/6c9f07bf8800171de2cd3f02815cebe1f4d45f2d
- stable/c/259caa711b7688365676442e2fdb286b8aceaa80
- stable/c/968550a439f64bd1a6c0d88efb92e4f082f84a26
- stable/c/a9551f26287debe6d8aa6e8841974661065b975f
- stable/c/c82b797abe668d0b668601a93ba2c0b071a63574