CVE-2024-47679: vfs: fix race between evice_inodes() and find_inode()&iput()

Published Oct 21, 2024
·
Updated

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

vfs: fix race between eviceinodes() and findinode()&iput()

Hi, all

Recently I noticed a bug[1] in btrfs, after digged it into and I believe it'a race in vfs.

Let's assume there's a inode (ie ino 261) with icount 1 is called by iput(), and there's a concurrent thread calling genericshutdownsuper().

cpu0: cpu1: iput() // icount is 1 ->spinlock(inode) ->dec icount to 0 ->iputfinal() genericshutdownsuper() ->inodeaddlru() ->evictinodes() // cause some reason[2] ->if (atomicread(inode->icount)) continue; // return before // inode 261 passed the above check // listlruaddobj() // and then schedule out ->spinunlock() // note here: the inode 261 // was still at sb list and hash list, // and IFREEING|IWILLFREE was not been set

btrfsiget() // after some function calls ->findinode() // found the above inode 261 ->spinlock(inode) // check IFREEING|IWILLFREE // and passed ->iget() ->spinunlock(inode) // schedule back ->spinlock(inode) // check (INEW|IFREEING|IWILLFREE) flags, // passed and set IFREEING iput() ->spinunlock(inode) ->spinlock(inode) ->evict() // dec icount to 0 ->iputfinal() ->spinunlock() ->evict()

Now, we have two threads simultaneously evicting the same inode, which may trigger the BUG(inode->istate & ICLEAR) statement both within clearinode() and iput().

To fix the bug, recheck the inode->icount after holding ilock. Because in the most scenarios, the first check is valid, and the overhead of spinlock() can be reduced.

If there is any misunderstanding, please let me know, thanks.

[1]: https://lore.kernel.org/linux-btrfs/000000000000eabe1d0619c48986@google.com/ [2]: The reason might be 1. SBACTIVE was removed or 2. mappingshrinkable() return false when I reproduced the bug.

Other sources

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

vfs: fix race between eviceinodes() and findinode()&iput()

Hi, all

Recently I noticed a bug[1] in btrfs, after digged it into and I believe it'a race in vfs.

Let's assume there's a inode (ie ino 261) with icount 1 is called by iput(), and there's a concurrent thread calling genericshutdownsuper().

cpu0: cpu1: iput() // icount is 1 -spinlock(inode) -dec icount to 0 -iputfinal() genericshutdownsuper() -inodeaddlru() -evictinodes() // cause some reason[2] -if (atomicread(inode-icount)) continue; // return before // inode 261 passed the above check // listlruaddobj() // and then schedule out -spinunlock() // note here: the inode 261 // was still at sb list and hash list, // and IFREEING|IWILLFREE was not been set

btrfsiget() // after some function calls -findinode() // found the above inode 261 -spinlock(inode) // check IFREEING|IWILLFREE // and passed -iget() -spinunlock(inode) // schedule back -spinlock(inode) // check (INEW|IFREEING|IWILLFREE) flags, // passed and set IFREEING iput() -spinunlock(inode) -spinlock(inode) -evict() // dec icount to 0 -iputfinal() -spinunlock() -evict()

Now, we have two threads simultaneously evicting the same inode, which may trigger the BUG(inode-istate & ICLEAR) statement both within clearinode() and iput().

To fix the bug, recheck the inode-icount after holding ilock. Because in the most scenarios, the first check is valid, and the overhead of spinlock() can be reduced.

If there is any misunderstanding, please let me know, thanks.

[1]:

— IBM

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

— Launchpad

Affected Software

217 affected componentsFixes available
Linux Linux kernel>=2.6.37<5.10.227
Linux Linux kernel>=5.11<5.15.168
Linux Linux kernel>=5.16<6.1.113
Linux Linux kernel>=6.2<6.6.54
Linux Linux kernel>=6.7<6.10.13
Linux Linux kernel>=6.11<6.11.2
IBM Verify Identity Access<=11.0 - 11.0.2
IBM Security Verify Access<=10.0 - 10.0.9.1
IBM Verify Identity Access Container<=11.0 - 11.0.2
IBM Security Verify Access Container<=10.0 - 10.0.9.1
debian/linux<6.1.115-1
6.1.115-1
debian/linux<6.11.2-1
6.11.2-1
debian/linux<6.11.2-1
6.11.2-1
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1
ubuntu/linux*
ubuntu/linux-aws*
ubuntu/linux-azure*
ubuntu/linux-lts-xenial*
ubuntu/linux*
ubuntu/linux-aws*
ubuntu/linux-aws-hwe*
ubuntu/linux-azure*
ubuntu/linux-gcp*
ubuntu/linux-hwe*
ubuntu/linux-hwe-edge*
ubuntu/linux-kvm*
ubuntu/linux-oracle*
ubuntu/linux-fips*
ubuntu/linux-fips*
ubuntu/linux*
ubuntu/linux-aws*
ubuntu/linux-aws-5.0*
ubuntu/linux-aws-5.3*
ubuntu/linux-aws-5.4<5.4.0-1142.152~18.04.1
5.4.0-1142.152~18.04.1
ubuntu/linux-azure*
ubuntu/linux-azure-4.15*
ubuntu/linux-azure-5.3*
ubuntu/linux-azure-5.4<5.4.0-1145.152~18.04.1
5.4.0-1145.152~18.04.1
ubuntu/linux-azure-edge*
ubuntu/linux-gcp*
ubuntu/linux-gcp-4.15*
ubuntu/linux-gcp-5.3*
ubuntu/linux-gcp-5.4<5.4.0-1143.152~18.04.1
5.4.0-1143.152~18.04.1
ubuntu/linux-gke-4.15*
ubuntu/linux-gke-5.4*
ubuntu/linux-gkeop-5.4*
ubuntu/linux-hwe*
ubuntu/linux-hwe-5.4<5.4.0-208.228~18.04.1
5.4.0-208.228~18.04.1
ubuntu/linux-hwe-edge*
ubuntu/linux-ibm-5.4<5.4.0-1086.91~18.04.1
5.4.0-1086.91~18.04.1
ubuntu/linux-kvm*
ubuntu/linux-oem*
ubuntu/linux-oracle*
ubuntu/linux-oracle-5.0*
ubuntu/linux-oracle-5.3*
ubuntu/linux-oracle-5.4<5.4.0-1138.147~18.04.1
5.4.0-1138.147~18.04.1
ubuntu/linux-raspi-5.4<5.4.0-1129.142~18.04.1
5.4.0-1129.142~18.04.1
ubuntu/linux-aws-fips*
ubuntu/linux-azure-fips*
ubuntu/linux-fips*
ubuntu/linux-gcp-fips*
ubuntu/linux-aws-fips*
ubuntu/linux-azure-fips*
ubuntu/linux-fips*
ubuntu/linux-gcp-fips*
ubuntu/linux<5.4.0-208.228
5.4.0-208.228
ubuntu/linux-aws<5.4.0-1140.150
5.4.0-1140.150
ubuntu/linux-aws-5.15<5.15.0-1073.79~20.04.1
5.15.0-1073.79~20.04.1
ubuntu/linux-azure<5.4.0-1145.152
5.4.0-1145.152
ubuntu/linux-azure-5.15<5.15.0-1078.87~20.04.1
5.15.0-1078.87~20.04.1
ubuntu/linux-bluefield<5.4.0-1099.106
5.4.0-1099.106
ubuntu/linux-gcp<5.4.0-1143.152
5.4.0-1143.152
ubuntu/linux-gcp-5.15<5.15.0-1072.80~20.04.1
5.15.0-1072.80~20.04.1
ubuntu/linux-hwe-5.15<5.15.0-127.137~20.04.1
5.15.0-127.137~20.04.1
ubuntu/linux-ibm<5.4.0-1086.91
5.4.0-1086.91
ubuntu/linux-ibm-5.15<5.15.0-1066.69~20.04.1
5.15.0-1066.69~20.04.1
ubuntu/linux-intel-iotg-5.15<5.15.0-1071.77~20.04.1
5.15.0-1071.77~20.04.1
ubuntu/linux-iot<5.4.0-1048.51
5.4.0-1048.51
ubuntu/linux-kvm<5.4.0-1127.136
5.4.0-1127.136
ubuntu/linux-lowlatency-hwe-5.15<5.15.0-127.137~20.04.1
5.15.0-127.137~20.04.1
ubuntu/linux-nvidia-tegra-5.15<5.15.0-1032.32~20.04.1
5.15.0-1032.32~20.04.1
ubuntu/linux-oracle<5.4.0-1138.147
5.4.0-1138.147
ubuntu/linux-oracle-5.15<5.15.0-1071.77~20.04.1
5.15.0-1071.77~20.04.1
ubuntu/linux-raspi<5.4.0-1129.142
5.4.0-1129.142
ubuntu/linux-riscv-5.15<5.15.0-1069.73~20.04.1
5.15.0-1069.73~20.04.1
ubuntu/linux-xilinx-zynqmp<5.4.0-1058.62
5.4.0-1058.62
ubuntu/linux-aws-5.11*
ubuntu/linux-aws-5.13*
ubuntu/linux-aws-5.8*
ubuntu/linux-azure-5.11*
ubuntu/linux-azure-5.13*
ubuntu/linux-azure-5.8*
ubuntu/linux-azure-fde*
ubuntu/linux-gcp-5.11*
ubuntu/linux-gcp-5.13*
ubuntu/linux-gcp-5.8*
ubuntu/linux-gke*
ubuntu/linux-gke-5.15*
ubuntu/linux-gkeop*
ubuntu/linux-gkeop-5.15*
ubuntu/linux-hwe-5.11*
ubuntu/linux-hwe-5.13*
ubuntu/linux-hwe-5.8*
ubuntu/linux-intel-5.13*
ubuntu/linux-oem-5.10*
ubuntu/linux-oem-5.13*
ubuntu/linux-oem-5.6*
ubuntu/linux-oracle-5.11*
ubuntu/linux-oracle-5.13*
ubuntu/linux-oracle-5.8*
ubuntu/linux-raspi2*
ubuntu/linux-riscv*
ubuntu/linux-riscv-5.11*
ubuntu/linux-riscv-5.8*
ubuntu/linux-aws-fips<5.4.0-1140.151+fips1
5.4.0-1140.151+fips1
ubuntu/linux-azure-fips<5.4.0-1145.152+fips1
5.4.0-1145.152+fips1
ubuntu/linux-fips<5.4.0-1116.126
5.4.0-1116.126
ubuntu/linux-gcp-fips<5.4.0-1143.152+fips1
5.4.0-1143.152+fips1
ubuntu/linux-aws-fips*
ubuntu/linux-azure-fips*
ubuntu/linux-fips*
ubuntu/linux-gcp-fips*
ubuntu/linux<5.15.0-127.137
5.15.0-127.137
ubuntu/linux-allwinner-5.19*
ubuntu/linux-aws<5.15.0-1073.79
5.15.0-1073.79
ubuntu/linux-aws-5.19*
ubuntu/linux-aws-6.2*
ubuntu/linux-aws-6.5*
ubuntu/linux-aws-6.8<6.8.0-1023.25~22.04.1
6.8.0-1023.25~22.04.1
ubuntu/linux-azure<5.15.0-1078.87
5.15.0-1078.87
ubuntu/linux-azure-5.19*
ubuntu/linux-azure-6.2*
ubuntu/linux-azure-6.5*
ubuntu/linux-azure-6.8<6.8.0-1025.30~22.04.1
6.8.0-1025.30~22.04.1
ubuntu/linux-azure-fde<5.15.0-1078.87.1
5.15.0-1078.87.1
ubuntu/linux-azure-fde-5.19*
ubuntu/linux-azure-fde-6.2*
ubuntu/linux-gcp<5.15.0-1072.80
5.15.0-1072.80
ubuntu/linux-gcp-5.19*
ubuntu/linux-gcp-6.2*
ubuntu/linux-gcp-6.5*
ubuntu/linux-gcp-6.8<6.8.0-1024.26~22.04.1
6.8.0-1024.26~22.04.1
ubuntu/linux-gke<5.15.0-1070.76
5.15.0-1070.76
ubuntu/linux-gkeop<5.15.0-1056.63
5.15.0-1056.63
ubuntu/linux-hwe-5.19*
ubuntu/linux-hwe-6.2*
ubuntu/linux-hwe-6.5*
ubuntu/linux-hwe-6.8<6.8.0-57.59~22.04.1
6.8.0-57.59~22.04.1
ubuntu/linux-ibm<5.15.0-1066.69
5.15.0-1066.69
ubuntu/linux-ibm-6.8<6.8.0-1023.23~22.04.1
6.8.0-1023.23~22.04.1
ubuntu/linux-intel-iotg<5.15.0-1071.77
5.15.0-1071.77
ubuntu/linux-kvm<5.15.0-1070.75
5.15.0-1070.75
ubuntu/linux-lowlatency<5.15.0-127.137
5.15.0-127.137
ubuntu/linux-lowlatency-hwe-5.19*
ubuntu/linux-lowlatency-hwe-6.2*
ubuntu/linux-lowlatency-hwe-6.5*
ubuntu/linux-lowlatency-hwe-6.8<6.8.0-54.56.1~22.04.1
6.8.0-54.56.1~22.04.1
ubuntu/linux-nvidia<5.15.0-1068.69
5.15.0-1068.69
ubuntu/linux-nvidia-6.2*
ubuntu/linux-nvidia-6.5*
ubuntu/linux-nvidia-6.8<6.8.0-1022.25~22.04.2
6.8.0-1022.25~22.04.2
ubuntu/linux-nvidia-tegra<5.15.0-1032.32
5.15.0-1032.32
ubuntu/linux-nvidia-tegra-igx<5.15.0-1020.20
5.15.0-1020.20
ubuntu/linux-oem-5.17*
ubuntu/linux-oem-6.0*
ubuntu/linux-oem-6.1*
ubuntu/linux-oem-6.5*
ubuntu/linux-oracle<5.15.0-1071.77
5.15.0-1071.77
ubuntu/linux-oracle-6.5*
ubuntu/linux-oracle-6.8<6.8.0-1020.21~22.04.1
6.8.0-1020.21~22.04.1
ubuntu/linux-raspi<5.15.0-1066.69
5.15.0-1066.69
ubuntu/linux-realtime*
ubuntu/linux-riscv*
ubuntu/linux-riscv-5.19*
ubuntu/linux-riscv-6.5*
ubuntu/linux-riscv-6.8<6.8.0-53.55.1~22.04.1
6.8.0-53.55.1~22.04.1
ubuntu/linux-starfive-5.19*
ubuntu/linux-starfive-6.2*
ubuntu/linux-starfive-6.5*
ubuntu/linux-xilinx-zynqmp<5.15.0-1039.43
5.15.0-1039.43
ubuntu/linux-bluefield<5.15.0-1057.59
5.15.0-1057.59
ubuntu/linux-intel-iot-realtime<5.15.0-1066.68
5.15.0-1066.68
ubuntu/linux-realtime<5.15.0-1074.82
5.15.0-1074.82
ubuntu/linux-realtime-6.8<6.8.1-1016.17~22.04.1
6.8.1-1016.17~22.04.1
ubuntu/linux-aws-fips*
ubuntu/linux-azure-fips*
ubuntu/linux-fips*
ubuntu/linux-gcp-fips*
ubuntu/linux-aws-fips<5.15.0-1073.79+fips1
5.15.0-1073.79+fips1
ubuntu/linux-azure-fips<5.15.0-1078.87+fips1
5.15.0-1078.87+fips1
ubuntu/linux-fips<5.15.0-127.137+fips1
5.15.0-127.137+fips1
ubuntu/linux-gcp-fips<5.15.0-1072.80+fips1
5.15.0-1072.80+fips1
ubuntu/linux<6.8.0-54.56
6.8.0-54.56
ubuntu/linux-aws<6.8.0-1023.25
6.8.0-1023.25
ubuntu/linux-azure<6.8.0-1025.30
6.8.0-1025.30
ubuntu/linux-azure-6.11<6.11.0-1012.12~24.04.1
6.11.0-1012.12~24.04.1
ubuntu/linux-azure-nvidia<6.8.0-1014.15
6.8.0-1014.15
ubuntu/linux-gcp<6.8.0-1024.26
6.8.0-1024.26
ubuntu/linux-gcp-6.11<6.11.0-1011.11~24.04.1
6.11.0-1011.11~24.04.1
ubuntu/linux-gke<6.8.0-1019.23
6.8.0-1019.23
ubuntu/linux-gkeop<6.8.0-1006.8
6.8.0-1006.8
ubuntu/linux-ibm<6.8.0-1022.22
6.8.0-1022.22
ubuntu/linux-lowlatency<6.8.0-54.56.1
6.8.0-54.56.1
ubuntu/linux-nvidia<6.8.0-1022.25
6.8.0-1022.25
ubuntu/linux-nvidia-6.11<6.11.0-1007.7
6.11.0-1007.7
ubuntu/linux-nvidia-lowlatency<6.8.0-1022.25.2
6.8.0-1022.25.2
ubuntu/linux-oem-6.11<6.11.0-1015.15
6.11.0-1015.15
ubuntu/linux-oem-6.8<6.8.0-1024.24
6.8.0-1024.24
ubuntu/linux-oracle<6.8.0-1020.21
6.8.0-1020.21
ubuntu/linux-raspi<6.8.0-1019.23
6.8.0-1019.23
ubuntu/linux-realtime*
ubuntu/linux-riscv<6.8.0-53.55.1
6.8.0-53.55.1
ubuntu/linux-xilinx<6.8.0-1017.18
6.8.0-1017.18
ubuntu/linux-raspi-realtime<6.8.0-2018.19
6.8.0-2018.19
ubuntu/linux-realtime<6.8.1-1016.17
6.8.1-1016.17
ubuntu/linux-fips<6.8.0-78.78+fips1
6.8.0-78.78+fips1
ubuntu/linux-vmware*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.115-1
  2. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.11.2-1
  3. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1
  4. Upgrade

    Upgrade ubuntu/linux-aws-5.4 to a version that resolves this vulnerability.

    Fixed in 5.4.0-1142.152~18.04.1
  5. Upgrade

    Upgrade ubuntu/linux-azure-5.4 to a version that resolves this vulnerability.

    Fixed in 5.4.0-1145.152~18.04.1
  6. Upgrade

    Upgrade ubuntu/linux-gcp-5.4 to a version that resolves this vulnerability.

    Fixed in 5.4.0-1143.152~18.04.1
  7. Upgrade

    Upgrade ubuntu/linux-hwe-5.4 to a version that resolves this vulnerability.

    Fixed in 5.4.0-208.228~18.04.1
  8. Upgrade

    Upgrade ubuntu/linux-ibm-5.4 to a version that resolves this vulnerability.

    Fixed in 5.4.0-1086.91~18.04.1
  9. Upgrade

    Upgrade ubuntu/linux-oracle-5.4 to a version that resolves this vulnerability.

    Fixed in 5.4.0-1138.147~18.04.1
  10. Upgrade

    Upgrade ubuntu/linux-raspi-5.4 to a version that resolves this vulnerability.

    Fixed in 5.4.0-1129.142~18.04.1
  11. Upgrade

    Upgrade ubuntu/linux to a version that resolves this vulnerability.

    Fixed in 5.4.0-208.228
  12. Upgrade

    Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.

    Fixed in 5.4.0-1140.150
  13. Upgrade

    Upgrade ubuntu/linux-aws-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1073.79~20.04.1
  14. Upgrade

    Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.

    Fixed in 5.4.0-1145.152
  15. Upgrade

    Upgrade ubuntu/linux-azure-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1078.87~20.04.1
  16. Upgrade

    Upgrade ubuntu/linux-bluefield to a version that resolves this vulnerability.

    Fixed in 5.4.0-1099.106
  17. Upgrade

    Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.

    Fixed in 5.4.0-1143.152
  18. Upgrade

    Upgrade ubuntu/linux-gcp-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1072.80~20.04.1
  19. Upgrade

    Upgrade ubuntu/linux-hwe-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-127.137~20.04.1
  20. Upgrade

    Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.

    Fixed in 5.4.0-1086.91
  21. Upgrade

    Upgrade ubuntu/linux-ibm-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1066.69~20.04.1
  22. Upgrade

    Upgrade ubuntu/linux-intel-iotg-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1071.77~20.04.1
  23. Upgrade

    Upgrade ubuntu/linux-iot to a version that resolves this vulnerability.

    Fixed in 5.4.0-1048.51
  24. Upgrade

    Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.

    Fixed in 5.4.0-1127.136
  25. Upgrade

    Upgrade ubuntu/linux-lowlatency-hwe-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-127.137~20.04.1
  26. Upgrade

    Upgrade ubuntu/linux-nvidia-tegra-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1032.32~20.04.1
  27. Upgrade

    Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.

    Fixed in 5.4.0-1138.147
  28. Upgrade

    Upgrade ubuntu/linux-oracle-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1071.77~20.04.1
  29. Upgrade

    Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.

    Fixed in 5.4.0-1129.142
  30. Upgrade

    Upgrade ubuntu/linux-riscv-5.15 to a version that resolves this vulnerability.

    Fixed in 5.15.0-1069.73~20.04.1
  31. Upgrade

    Upgrade ubuntu/linux-xilinx-zynqmp to a version that resolves this vulnerability.

    Fixed in 5.4.0-1058.62
  32. Upgrade

    Upgrade ubuntu/linux-aws-fips to a version that resolves this vulnerability.

    Fixed in 5.4.0-1140.151+fips1
  33. Upgrade

    Upgrade ubuntu/linux-azure-fips to a version that resolves this vulnerability.

    Fixed in 5.4.0-1145.152+fips1
  34. Upgrade

    Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.

    Fixed in 5.4.0-1116.126
  35. Upgrade

    Upgrade ubuntu/linux-gcp-fips to a version that resolves this vulnerability.

    Fixed in 5.4.0-1143.152+fips1
  36. Upgrade

    Upgrade ubuntu/linux to a version that resolves this vulnerability.

    Fixed in 5.15.0-127.137
  37. Upgrade

    Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.

    Fixed in 5.15.0-1073.79
  38. Upgrade

    Upgrade ubuntu/linux-aws-6.8 to a version that resolves this vulnerability.

    Fixed in 6.8.0-1023.25~22.04.1
  39. Upgrade

    Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.

    Fixed in 5.15.0-1078.87
  40. Upgrade

    Upgrade ubuntu/linux-azure-6.8 to a version that resolves this vulnerability.

    Fixed in 6.8.0-1025.30~22.04.1
  41. Upgrade

    Upgrade ubuntu/linux-azure-fde to a version that resolves this vulnerability.

    Fixed in 5.15.0-1078.87.1
  42. Upgrade

    Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.

    Fixed in 5.15.0-1072.80
  43. Upgrade

    Upgrade ubuntu/linux-gcp-6.8 to a version that resolves this vulnerability.

    Fixed in 6.8.0-1024.26~22.04.1
  44. Upgrade

    Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.

    Fixed in 5.15.0-1070.76
  45. Upgrade

    Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.

    Fixed in 5.15.0-1056.63
  46. Upgrade

    Upgrade ubuntu/linux-hwe-6.8 to a version that resolves this vulnerability.

    Fixed in 6.8.0-57.59~22.04.1
  47. Upgrade

    Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.

    Fixed in 5.15.0-1066.69
  48. Upgrade

    Upgrade ubuntu/linux-ibm-6.8 to a version that resolves this vulnerability.

    Fixed in 6.8.0-1023.23~22.04.1
  49. Upgrade

    Upgrade ubuntu/linux-intel-iotg to a version that resolves this vulnerability.

    Fixed in 5.15.0-1071.77
  50. Upgrade

    Upgrade ubuntu/linux-kvm to a version that resolves this vulnerability.

    Fixed in 5.15.0-1070.75
  51. Upgrade

    Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.

    Fixed in 5.15.0-127.137
  52. Upgrade

    Upgrade ubuntu/linux-lowlatency-hwe-6.8 to a version that resolves this vulnerability.

    Fixed in 6.8.0-54.56.1~22.04.1
  53. Upgrade

    Upgrade ubuntu/linux-nvidia to a version that resolves this vulnerability.

    Fixed in 5.15.0-1068.69
  54. Upgrade

    Upgrade ubuntu/linux-nvidia-6.8 to a version that resolves this vulnerability.

    Fixed in 6.8.0-1022.25~22.04.2
  55. Upgrade

    Upgrade ubuntu/linux-nvidia-tegra to a version that resolves this vulnerability.

    Fixed in 5.15.0-1032.32
  56. Upgrade

    Upgrade ubuntu/linux-nvidia-tegra-igx to a version that resolves this vulnerability.

    Fixed in 5.15.0-1020.20
  57. Upgrade

    Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.

    Fixed in 5.15.0-1071.77
  58. Upgrade

    Upgrade ubuntu/linux-oracle-6.8 to a version that resolves this vulnerability.

    Fixed in 6.8.0-1020.21~22.04.1
  59. Upgrade

    Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.

    Fixed in 5.15.0-1066.69
  60. Upgrade

    Upgrade ubuntu/linux-riscv-6.8 to a version that resolves this vulnerability.

    Fixed in 6.8.0-53.55.1~22.04.1
  61. Upgrade

    Upgrade ubuntu/linux-xilinx-zynqmp to a version that resolves this vulnerability.

    Fixed in 5.15.0-1039.43
  62. Upgrade

    Upgrade ubuntu/linux-bluefield to a version that resolves this vulnerability.

    Fixed in 5.15.0-1057.59
  63. Upgrade

    Upgrade ubuntu/linux-intel-iot-realtime to a version that resolves this vulnerability.

    Fixed in 5.15.0-1066.68
  64. Upgrade

    Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.

    Fixed in 5.15.0-1074.82
  65. Upgrade

    Upgrade ubuntu/linux-realtime-6.8 to a version that resolves this vulnerability.

    Fixed in 6.8.1-1016.17~22.04.1
  66. Upgrade

    Upgrade ubuntu/linux-aws-fips to a version that resolves this vulnerability.

    Fixed in 5.15.0-1073.79+fips1
  67. Upgrade

    Upgrade ubuntu/linux-azure-fips to a version that resolves this vulnerability.

    Fixed in 5.15.0-1078.87+fips1
  68. Upgrade

    Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.

    Fixed in 5.15.0-127.137+fips1
  69. Upgrade

    Upgrade ubuntu/linux-gcp-fips to a version that resolves this vulnerability.

    Fixed in 5.15.0-1072.80+fips1
  70. Upgrade

    Upgrade ubuntu/linux to a version that resolves this vulnerability.

    Fixed in 6.8.0-54.56
  71. Upgrade

    Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.

    Fixed in 6.8.0-1023.25
  72. Upgrade

    Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.

    Fixed in 6.8.0-1025.30
  73. Upgrade

    Upgrade ubuntu/linux-azure-6.11 to a version that resolves this vulnerability.

    Fixed in 6.11.0-1012.12~24.04.1
  74. Upgrade

    Upgrade ubuntu/linux-azure-nvidia to a version that resolves this vulnerability.

    Fixed in 6.8.0-1014.15
  75. Upgrade

    Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.

    Fixed in 6.8.0-1024.26
  76. Upgrade

    Upgrade ubuntu/linux-gcp-6.11 to a version that resolves this vulnerability.

    Fixed in 6.11.0-1011.11~24.04.1
  77. Upgrade

    Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.

    Fixed in 6.8.0-1019.23
  78. Upgrade

    Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.

    Fixed in 6.8.0-1006.8
  79. Upgrade

    Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.

    Fixed in 6.8.0-1022.22
  80. Upgrade

    Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.

    Fixed in 6.8.0-54.56.1
  81. Upgrade

    Upgrade ubuntu/linux-nvidia to a version that resolves this vulnerability.

    Fixed in 6.8.0-1022.25
  82. Upgrade

    Upgrade ubuntu/linux-nvidia-6.11 to a version that resolves this vulnerability.

    Fixed in 6.11.0-1007.7
  83. Upgrade

    Upgrade ubuntu/linux-nvidia-lowlatency to a version that resolves this vulnerability.

    Fixed in 6.8.0-1022.25.2
  84. Upgrade

    Upgrade ubuntu/linux-oem-6.11 to a version that resolves this vulnerability.

    Fixed in 6.11.0-1015.15
  85. Upgrade

    Upgrade ubuntu/linux-oem-6.8 to a version that resolves this vulnerability.

    Fixed in 6.8.0-1024.24
  86. Upgrade

    Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.

    Fixed in 6.8.0-1020.21
  87. Upgrade

    Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.

    Fixed in 6.8.0-1019.23
  88. Upgrade

    Upgrade ubuntu/linux-riscv to a version that resolves this vulnerability.

    Fixed in 6.8.0-53.55.1
  89. Upgrade

    Upgrade ubuntu/linux-xilinx to a version that resolves this vulnerability.

    Fixed in 6.8.0-1017.18
  90. Upgrade

    Upgrade ubuntu/linux-raspi-realtime to a version that resolves this vulnerability.

    Fixed in 6.8.0-2018.19
  91. Upgrade

    Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.

    Fixed in 6.8.1-1016.17
  92. Upgrade

    Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.

    Fixed in 6.8.0-78.78+fips1
  93. Compensating control

    In the VFS inode handling code, recheck inode->i_count after acquiring i_lock to fix the race between evict_inodes() and find_inode()/iput().

Event History

Oct 21, 2024
CVE Published
via MITRE·11:53 AM
Data Sourced
via MITRE·11:53 AM
DescriptionSeverity
Data Sourced
via Red Hat·12:01 PM
DescriptionSeverityAffected Software
Data Sourced
via OSV·12:15 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·12:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 8, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2024-47679?

CVE-2024-47679 has been classified as a medium severity vulnerability affecting the Linux kernel.

2

How do I fix CVE-2024-47679?

To mitigate CVE-2024-47679, users should upgrade to a patched version of the Linux kernel, specifically versions that are not vulnerable.

3

What versions of the Linux kernel are affected by CVE-2024-47679?

CVE-2024-47679 affects Linux kernel versions from 2.6.37 up to and including 6.11.2.

4

What type of vulnerability is CVE-2024-47679?

CVE-2024-47679 is characterized as a race condition vulnerability within the vfs subsystem of the Linux kernel.

5

Where can I find the details of the fix for CVE-2024-47679?

The details of the fix for CVE-2024-47679 can be reviewed in the change logs of the updated Linux kernel versions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203