Vulnerability · Published Jan 13, 2026 · Assigned by Linux

CVE-2025-68774hfsplus: fix missing hfs_bnode_get() in __hfs_bnode_create

High 7.5

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.6% (higher than 48% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.5High
Exploit odds (30 days)0.6%top 51.8% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: hfsplus: fix missing hfs_bnode_get() in __hfs_bnode_create When sync() and link() are called concurrently, both threads may enter hfs_bnode_find() without finding the node in the hash table and proceed to create it. Thread A: hfsplus_write_inode() -> hfsplus_write_system_inode() -> hfs_btree_write() -> hfs_bnode_find(tree, 0) -> __hfs_bnode_create(tree, 0) Thread B: hfsplus_create_cat() -> hfs_brec_insert() -> hfs_bnode_split() -> hfs_bmap_alloc() -> hfs_bnode_find(tree, 0) -> __hfs_bnode_create(tree, 0) In this case, thread A creates the bnode, sets refcnt=1, and hashes it. Thread B also tries to create the same bnode, notices it has already been inserted, drops its own instance, and uses the hashed one without getting the node. ``` node2 = hfs_bnode_findhash(tree, cnid); if (!node2) { <- Thread A hash = hfs_bnode_hash(cnid); node->next_hash = tree->node_hash[hash]; tree->node_hash[hash] = node; tree->node_hash_cnt++; } else { <- Thread B spin_unlock(&tree->hash_lock); kfree(node); wait_event(node2->lock_wq, !test_bit(HFS_BNODE_NEW, &node2->flags)); return node2; } ``` However, hfs_bnode_find() requires each call to take a reference. Here both threads end up setting refcnt=1. When they later put the node, this triggers: BUG_ON(!atomic_read(&node->refcnt)) In this scenario, Thread B in fact finds the node in the hash table rather than creating a new one, and thus must take a reference. Fix this by calling hfs_bnode_get() when reusing a bnode newly created by another thread to ensure the refcount is updated correctly. A similar bug was fixed in HFS long ago in commit a9dc087fd3c4 ("fix missing hfs_bnode_get() in __hfs_bnode_create") but the same issue remained in HFS+ until now.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.162-1DEBIAN-CVE-2025-68774
Debian:13linux6.12.69-1DSA-6126-1
Debian:13linux6.12.69-1DEBIAN-CVE-2025-68774
Debian:14linux6.18.3-1DEBIAN-CVE-2025-68774
Ubuntu:22.04:LTSlinux5.15.0-173.183UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux6.8.0-110.110UBUNTU-CVE-2025-68774
Ubuntu:25.10linux6.17.0-22.22UBUNTU-CVE-2025-68774
Ubuntu:25.10linux6.17.0-22.22USN-8177-1
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-aws5.15.0-1103.110UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-aws6.8.0-1052.55UBUNTU-CVE-2025-68774
Ubuntu:25.10linux-aws6.17.0-1012.12UBUNTU-CVE-2025-68774
Ubuntu:25.10linux-aws6.17.0-1012.12USN-8183-2
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-aws-6.176.17.0-1012.12~24.04.1UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-aws-6.176.17.0-1012.12~24.04.1USN-8183-2
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1052.55~22.04.1UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-azure5.15.0-1109.118UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-azure6.8.0-1054.60UBUNTU-CVE-2025-68774
Ubuntu:25.10linux-azure6.17.0-1013.13UBUNTU-CVE-2025-68774
Ubuntu:25.10linux-azure6.17.0-1013.13USN-8245-1
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-azure-6.176.17.0-1013.13~24.04.1USN-8245-1
Ubuntu:24.04:LTSlinux-azure-6.176.17.0-1013.13~24.04.1UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1059.65~22.04.1UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1109.118.1UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1058.65UBUNTU-CVE-2025-68774
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-azure-fde-6.86.8.0-1058.65~22.04.1UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-gcp5.15.0-1103.112UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-gcp6.8.0-1054.57UBUNTU-CVE-2025-68774
Ubuntu:25.10linux-gcp6.17.0-1012.12USN-8183-1
Ubuntu:25.10linux-gcp6.17.0-1012.12UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-gcp-6.176.17.0-1012.12~24.04.1UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-gcp-6.176.17.0-1012.12~24.04.1USN-8183-1
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1054.57~22.04.1UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-gke5.15.0-1099.105UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-gke6.8.0-1050.56UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1086.94UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1037.40UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-hwe-6.176.17.0-22.22~24.04.1UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-hwe-6.176.17.0-22.22~24.04.1USN-8183-2
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-110.110~22.04.1UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-ibm5.15.0-1097.100UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-ibm6.8.0-1051.51UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1051.51~22.04.1UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1098.104UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-kvm5.15.0-1095.100UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-173.183UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-110.110.1UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-110.110.1~22.04.1UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1098.99UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1051.54UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-nvidia-6.176.17.0-1018.18UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1051.54~22.04.1UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1051.54.1UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1055.55UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1022.22UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1044.44UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-oem-6.176.17.0-1020.20UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-oem-6.176.17.0-1020.20USN-8245-1
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-oracle5.15.0-1100.106UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-oracle6.8.0-1049.50UBUNTU-CVE-2025-68774
Ubuntu:25.10linux-oracle6.17.0-1011.11USN-8183-2
Ubuntu:25.10linux-oracle6.17.0-1011.11UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-oracle-6.176.17.0-1011.11~24.04.1USN-8183-2
Ubuntu:24.04:LTSlinux-oracle-6.176.17.0-1011.11~24.04.1UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1049.50~22.04.1UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-raspi5.15.0-1097.100UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-raspi6.8.0-1052.56UBUNTU-CVE-2025-68774
Ubuntu:25.10linux-raspi6.17.0-1013.13UBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-68774
Ubuntu:25.10linux-realtime6.17.0-1010.11USN-8177-1
Ubuntu:25.10linux-realtime6.17.0-1010.11UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-68774
Ubuntu:25.10linux-riscv6.17.0-22.22.1UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-riscv-6.176.17.0-22.22.1~24.04.1UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-110.110~22.04.1UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2025-68774
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1028.29UBUNTU-CVE-2025-68774
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1067.71UBUNTU-CVE-2025-68774

Affected products (as reported)

VendorProductVersions
Linux Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 3b0fc7af50b896d0f3d104e70787ba1973bc0b561da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 39e149d58ef4d7883cbf87448d39d51292fd342d1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before b68dc4134b18a3922cd33439ec614aad4172bc861da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before b9d1c6bb5f19460074ce9862cb80be86b5fb0a501da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 457f795e7abd7770de10216d7f9994a3f12a56d61da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 5882e7c8cdbb5e254a69628b780acff89c78071e1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 152af114287851583cf7e0abc10129941f19466a
Linux Linux 2.6.12

References