Към съдържанието
Търсене

CVE-2026-74363: Linux

7.8

CVSS 3.1

Няма данни

Вероятност да бъде експлоатирана в следващите 30 дни (EPSS)

Няма потвърждение

Атакува се

Няма данни

Време до експлоатация

Атакува се локално, без особени условия, с обикновен потребителски вход и без действие от потребителя.

  • Експлоатация: няма данни за експлоатация
  • Атаката не може да се автоматизира

Описание

Оригинално описание

In the Linux kernel, the following vulnerability has been resolved: bpf: fix UAF by restoring RCU-delayed inode freeing in bpffs commit 4f375ade6aa9 ("bpf: Avoid RCU context warning when unpinning htab with internal structs") moved inode cleanup from ->free_inode() into ->destroy_inode() to avoid sleeping in RCU context when calling bpf_any_put(). However this removed the RCU delay on freeing the inode itself and the cached symlink body (i_link), both of which can be accessed by RCU pathwalk (pick_link, may_lookup etc.). This causes a use-after-free when a concurrent unlinkat() drops the last inode reference and destroy_inode() frees the inode immediately, while another task is still walking the path in RCU mode and reads inode->i_opflags (offset +2) inside current_time() -> is_mgtime(). KASAN reports: BUG: KASAN: slab-use-after-free in is_mgtime include/linux/fs.h:2313 Read of size 2 at addr ffff8880407e4282 (offset +2 = i_opflags) The rules (per Al Viro): ->destroy_inode() called immediately, can sleep, use for blocking cleanup e.g. bpf_any_put() ->free_inode() called after RCU grace period, use for freeing inode and anything RCU-accessible e.g. i_link Fix: split the two concerns properly: - keep bpf_any_put() in bpf_destroy_inode() since it is blocking and needs to run promptly - introduce bpf_free_inode() to handle kfree(i_link) and free_inode_nonrcu() with proper RCU delay, preventing the UAF

Засегнати продукти

  • Linux Linux: e28616ca3d67e745ecb2f10eba4a626e1fc9a203 преди ea1c243c39e32b7fc1c2edfe32081ff7e30a877c; 743a620c661994c7f0938e6dd32fb0883fb1e0ea преди 5fecb71c10c28aef276ba49c718dc961745fdcf0; b6e9645be9eb93f7aff3ca887f8edb6f1d63358f преди c70d0f9114c3cc156f6029a400c4eb7e6f7c82b2; ee04cff9ed4d6bb25802f5cecfcd0750500410f3 преди 53649846e0437d1d9b7cb993cfe54c367addf7ae; 4f375ade6aa9f37fd72d7a78682f639772089eed преди 61f19729728243c82476dee31315143ed3275e7f; 4f375ade6aa9f37fd72d7a78682f639772089eed преди 0497ff765746d9b2d17445c8f7cc737b36c0152a; 4f375ade6aa9f37fd72d7a78682f639772089eed преди b93c55b4932dd7e32dca8cf34a3443cc87a02906; de2d2baecc84cc7fca52eec2b9b55d89c93e3565; 5.15.195 преди 5.15.212; 6.1.157 преди 6.1.178; 6.6.113 преди 6.6.145; 6.12.54 преди 6.12.97; 6.17.4 преди 6.18
  • Linux Linux: 6.18; преди 6.18; 5.15.212 до 5.15.*; 6.1.178 до 6.1.*; 6.6.145 до 6.6.*; 6.12.97 до 6.12.*; 6.18.40 до 6.18.*; 7.1.5 до 7.1.*; от 7.2 нататък

История

  • 15 август 2026 Публикувано

Други уязвимости в Linux Linux

Първоизточници

CVE-2026-74363: Linux | freedomonline.bg