Vulnerability-Lookup

GHSA-62RP-R79H-7Q8X

Vulnerability from github – Published: 2026-05-27 15:33 – Updated: 2026-06-24 18:32

Details

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

btrfs: fix EEXIST abort due to non-consecutive gaps in chunk allocation

I have been observing a number of systems aborting at insert_dev_extents() in btrfs_create_pending_block_groups(). The following is a sample stack trace of such an abort coming from forced chunk allocation (typically behind CONFIG_BTRFS_EXPERIMENTAL) but this can theoretically happen to any DUP chunk allocation.

[81.801] ------------[ cut here ]------------ [81.801] BTRFS: Transaction aborted (error -17) [81.801] WARNING: fs/btrfs/block-group.c:2876 at btrfs_create_pending_block_groups+0x721/0x770 [btrfs], CPU#1: bash/319 [81.802] Modules linked in: virtio_net btrfs xor zstd_compress raid6_pq null_blk [81.803] CPU: 1 UID: 0 PID: 319 Comm: bash Kdump: loaded Not tainted 6.19.0-rc6+ #319 NONE [81.803] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.17.0-2-2 04/01/2014 [81.804] RIP: 0010:btrfs_create_pending_block_groups+0x723/0x770 [btrfs] [81.806] RSP: 0018:ffffa36241a6bce8 EFLAGS: 00010282 [81.806] RAX: 000000000000000d RBX: ffff8e699921e400 RCX: 0000000000000000 [81.807] RDX: 0000000002040001 RSI: 00000000ffffffef RDI: ffffffffc0608bf0 [81.807] RBP: 00000000ffffffef R08: ffff8e69830f6000 R09: 0000000000000007 [81.808] R10: ffff8e699921e5e8 R11: 0000000000000000 R12: ffff8e6999228000 [81.808] R13: ffff8e6984d82000 R14: ffff8e69966a69c0 R15: ffff8e69aa47b000 [81.809] FS: 00007fec6bdd9740(0000) GS:ffff8e6b1b379000(0000) knlGS:0000000000000000 [81.809] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [81.810] CR2: 00005604833670f0 CR3: 0000000116679000 CR4: 00000000000006f0 [81.810] Call Trace: [81.810] [81.810] __btrfs_end_transaction+0x3e/0x2b0 [btrfs] [81.811] btrfs_force_chunk_alloc_store+0xcd/0x140 [btrfs] [81.811] kernfs_fop_write_iter+0x15f/0x240 [81.812] vfs_write+0x264/0x500 [81.812] ksys_write+0x6c/0xe0 [81.812] do_syscall_64+0x66/0x770 [81.812] entry_SYSCALL_64_after_hwframe+0x76/0x7e [81.813] RIP: 0033:0x7fec6be66197 [81.814] RSP: 002b:00007fffb159dd30 EFLAGS: 00000202 ORIG_RAX: 0000000000000001 [81.815] RAX: ffffffffffffffda RBX: 00007fec6bdd9740 RCX: 00007fec6be66197 [81.815] RDX: 0000000000000002 RSI: 0000560483374f80 RDI: 0000000000000001 [81.816] RBP: 0000560483374f80 R08: 0000000000000000 R09: 0000000000000000 [81.816] R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000002 [81.817] R13: 00007fec6bfb85c0 R14: 00007fec6bfb5ee0 R15: 00005604833729c0 [81.817] [81.817] irq event stamp: 20039 [81.818] hardirqs last enabled at (20047): [] __up_console_sem+0x52/0x60 [81.818] hardirqs last disabled at (20056): [] __up_console_sem+0x37/0x60 [81.819] softirqs last enabled at (19470): [] __irq_exit_rcu+0x96/0xc0 [81.819] softirqs last disabled at (19463): [] __irq_exit_rcu+0x96/0xc0 [81.820] ---[ end trace 0000000000000000 ]--- [81.820] BTRFS: error (device dm-7 state A) in btrfs_create_pending_block_groups:2876: errno=-17 Object already exists

Inspecting these aborts with drgn, I observed a pattern of overlapping chunk_maps. Note how stripe 1 of the first chunk overlaps in physical address with stripe 0 of the second chunk.

Physical Start Physical End Length Logical Type Stripe

0x0000000102500000 0x0000000142500000 1.0G 0x0000000641d00000 META|DUP 0/2 0x0000000142500000 0x0000000182500000 1.0G 0x0000000641d00000 META|DUP 1/2 0x0000000142500000 0x0000000182500000 1.0G 0x0000000601d00000 META|DUP 0/2 0x0000000182500000 0x00000001c2500000 1.0G 0x0000000601d00000 META|DUP 1/2

Now how could this possibly happen? All chunk allocation is ---truncated---

Severity

5.5 (Medium)


                  
                    CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-45934"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-05-27T14:17:09Z",
    "severity": "MODERATE"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix EEXIST abort due to non-consecutive gaps in chunk allocation\n\nI have been observing a number of systems aborting at\ninsert_dev_extents() in btrfs_create_pending_block_groups(). The\nfollowing is a sample stack trace of such an abort coming from forced\nchunk allocation (typically behind CONFIG_BTRFS_EXPERIMENTAL) but this\ncan theoretically happen to any DUP chunk allocation.\n\n  [81.801] ------------[ cut here ]------------\n  [81.801] BTRFS: Transaction aborted (error -17)\n  [81.801] WARNING: fs/btrfs/block-group.c:2876 at btrfs_create_pending_block_groups+0x721/0x770 [btrfs], CPU#1: bash/319\n  [81.802] Modules linked in: virtio_net btrfs xor zstd_compress raid6_pq null_blk\n  [81.803] CPU: 1 UID: 0 PID: 319 Comm: bash Kdump: loaded Not tainted 6.19.0-rc6+ #319 NONE\n  [81.803] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.17.0-2-2 04/01/2014\n  [81.804] RIP: 0010:btrfs_create_pending_block_groups+0x723/0x770 [btrfs]\n  [81.806] RSP: 0018:ffffa36241a6bce8 EFLAGS: 00010282\n  [81.806] RAX: 000000000000000d RBX: ffff8e699921e400 RCX: 0000000000000000\n  [81.807] RDX: 0000000002040001 RSI: 00000000ffffffef RDI: ffffffffc0608bf0\n  [81.807] RBP: 00000000ffffffef R08: ffff8e69830f6000 R09: 0000000000000007\n  [81.808] R10: ffff8e699921e5e8 R11: 0000000000000000 R12: ffff8e6999228000\n  [81.808] R13: ffff8e6984d82000 R14: ffff8e69966a69c0 R15: ffff8e69aa47b000\n  [81.809] FS:  00007fec6bdd9740(0000) GS:ffff8e6b1b379000(0000) knlGS:0000000000000000\n  [81.809] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  [81.810] CR2: 00005604833670f0 CR3: 0000000116679000 CR4: 00000000000006f0\n  [81.810] Call Trace:\n  [81.810]  \u003cTASK\u003e\n  [81.810]  __btrfs_end_transaction+0x3e/0x2b0 [btrfs]\n  [81.811]  btrfs_force_chunk_alloc_store+0xcd/0x140 [btrfs]\n  [81.811]  kernfs_fop_write_iter+0x15f/0x240\n  [81.812]  vfs_write+0x264/0x500\n  [81.812]  ksys_write+0x6c/0xe0\n  [81.812]  do_syscall_64+0x66/0x770\n  [81.812]  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  [81.813] RIP: 0033:0x7fec6be66197\n  [81.814] RSP: 002b:00007fffb159dd30 EFLAGS: 00000202 ORIG_RAX: 0000000000000001\n  [81.815] RAX: ffffffffffffffda RBX: 00007fec6bdd9740 RCX: 00007fec6be66197\n  [81.815] RDX: 0000000000000002 RSI: 0000560483374f80 RDI: 0000000000000001\n  [81.816] RBP: 0000560483374f80 R08: 0000000000000000 R09: 0000000000000000\n  [81.816] R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000002\n  [81.817] R13: 00007fec6bfb85c0 R14: 00007fec6bfb5ee0 R15: 00005604833729c0\n  [81.817]  \u003c/TASK\u003e\n  [81.817] irq event stamp: 20039\n  [81.818] hardirqs last  enabled at (20047): [\u003cffffffff99a68302\u003e] __up_console_sem+0x52/0x60\n  [81.818] hardirqs last disabled at (20056): [\u003cffffffff99a682e7\u003e] __up_console_sem+0x37/0x60\n  [81.819] softirqs last  enabled at (19470): [\u003cffffffff999d2b46\u003e] __irq_exit_rcu+0x96/0xc0\n  [81.819] softirqs last disabled at (19463): [\u003cffffffff999d2b46\u003e] __irq_exit_rcu+0x96/0xc0\n  [81.820] ---[ end trace 0000000000000000 ]---\n  [81.820] BTRFS: error (device dm-7 state A) in btrfs_create_pending_block_groups:2876: errno=-17 Object already exists\n\nInspecting these aborts with drgn, I observed a pattern of overlapping\nchunk_maps. Note how stripe 1 of the first chunk overlaps in physical\naddress with stripe 0 of the second chunk.\n\nPhysical Start     Physical End       Length       Logical            Type                 Stripe\n----------------------------------------------------------------------------------------------------\n0x0000000102500000 0x0000000142500000 1.0G         0x0000000641d00000 META|DUP             0/2\n0x0000000142500000 0x0000000182500000 1.0G         0x0000000641d00000 META|DUP             1/2\n0x0000000142500000 0x0000000182500000 1.0G         0x0000000601d00000 META|DUP             0/2\n0x0000000182500000 0x00000001c2500000 1.0G         0x0000000601d00000 META|DUP             1/2\n\nNow how could this possibly happen? All chunk allocation is\n---truncated---",
  "id": "GHSA-62rp-r79h-7q8x",
  "modified": "2026-06-24T18:32:28Z",
  "published": "2026-05-27T15:33:17Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-45934"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/156cac365e27a82b64ae510c5f463fd81f0265b1"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7d4eadee7042d27fcea659fcdd738f463a7d2e70"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b14c5e04bd0f722ed631845599d52d03fcae1bc1"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}

CVE-2026-45934 (GCVE-0-2026-45934)

Vulnerability from cvelistv5 – Published: 2026-05-27 12:17 – Updated: 2026-05-27 12:17

Title

btrfs: fix EEXIST abort due to non-consecutive gaps in chunk allocation

Summary

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix EEXIST abort due to non-consecutive gaps in chunk allocation I have been observing a number of systems aborting at insert_dev_extents() in btrfs_create_pending_block_groups(). The following is a sample stack trace of such an abort coming from forced chunk allocation (typically behind CONFIG_BTRFS_EXPERIMENTAL) but this can theoretically happen to any DUP chunk allocation. [81.801] ------------[ cut here ]------------ [81.801] BTRFS: Transaction aborted (error -17) [81.801] WARNING: fs/btrfs/block-group.c:2876 at btrfs_create_pending_block_groups+0x721/0x770 [btrfs], CPU#1: bash/319 [81.802] Modules linked in: virtio_net btrfs xor zstd_compress raid6_pq null_blk [81.803] CPU: 1 UID: 0 PID: 319 Comm: bash Kdump: loaded Not tainted 6.19.0-rc6+ #319 NONE [81.803] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.17.0-2-2 04/01/2014 [81.804] RIP: 0010:btrfs_create_pending_block_groups+0x723/0x770 [btrfs] [81.806] RSP: 0018:ffffa36241a6bce8 EFLAGS: 00010282 [81.806] RAX: 000000000000000d RBX: ffff8e699921e400 RCX: 0000000000000000 [81.807] RDX: 0000000002040001 RSI: 00000000ffffffef RDI: ffffffffc0608bf0 [81.807] RBP: 00000000ffffffef R08: ffff8e69830f6000 R09: 0000000000000007 [81.808] R10: ffff8e699921e5e8 R11: 0000000000000000 R12: ffff8e6999228000 [81.808] R13: ffff8e6984d82000 R14: ffff8e69966a69c0 R15: ffff8e69aa47b000 [81.809] FS: 00007fec6bdd9740(0000) GS:ffff8e6b1b379000(0000) knlGS:0000000000000000 [81.809] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [81.810] CR2: 00005604833670f0 CR3: 0000000116679000 CR4: 00000000000006f0 [81.810] Call Trace: [81.810] <TASK> [81.810] __btrfs_end_transaction+0x3e/0x2b0 [btrfs] [81.811] btrfs_force_chunk_alloc_store+0xcd/0x140 [btrfs] [81.811] kernfs_fop_write_iter+0x15f/0x240 [81.812] vfs_write+0x264/0x500 [81.812] ksys_write+0x6c/0xe0 [81.812] do_syscall_64+0x66/0x770 [81.812] entry_SYSCALL_64_after_hwframe+0x76/0x7e [81.813] RIP: 0033:0x7fec6be66197 [81.814] RSP: 002b:00007fffb159dd30 EFLAGS: 00000202 ORIG_RAX: 0000000000000001 [81.815] RAX: ffffffffffffffda RBX: 00007fec6bdd9740 RCX: 00007fec6be66197 [81.815] RDX: 0000000000000002 RSI: 0000560483374f80 RDI: 0000000000000001 [81.816] RBP: 0000560483374f80 R08: 0000000000000000 R09: 0000000000000000 [81.816] R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000002 [81.817] R13: 00007fec6bfb85c0 R14: 00007fec6bfb5ee0 R15: 00005604833729c0 [81.817] </TASK> [81.817] irq event stamp: 20039 [81.818] hardirqs last enabled at (20047): [<ffffffff99a68302>] __up_console_sem+0x52/0x60 [81.818] hardirqs last disabled at (20056): [<ffffffff99a682e7>] __up_console_sem+0x37/0x60 [81.819] softirqs last enabled at (19470): [<ffffffff999d2b46>] __irq_exit_rcu+0x96/0xc0 [81.819] softirqs last disabled at (19463): [<ffffffff999d2b46>] __irq_exit_rcu+0x96/0xc0 [81.820] ---[ end trace 0000000000000000 ]--- [81.820] BTRFS: error (device dm-7 state A) in btrfs_create_pending_block_groups:2876: errno=-17 Object already exists Inspecting these aborts with drgn, I observed a pattern of overlapping chunk_maps. Note how stripe 1 of the first chunk overlaps in physical address with stripe 0 of the second chunk. Physical Start Physical End Length Logical Type Stripe ---------------------------------------------------------------------------------------------------- 0x0000000102500000 0x0000000142500000 1.0G 0x0000000641d00000 META|DUP 0/2 0x0000000142500000 0x0000000182500000 1.0G 0x0000000641d00000 META|DUP 1/2 0x0000000142500000 0x0000000182500000 1.0G 0x0000000601d00000 META|DUP 0/2 0x0000000182500000 0x00000001c2500000 1.0G 0x0000000601d00000 META|DUP 1/2 Now how could this possibly happen? All chunk allocation is ---truncated---

Severity

No CVSS data available.

Assigner

Linux mitre root

References

3 references

URL	Tags
https://git.kernel.org/stable/c/7d4eadee7042d27fc…
https://git.kernel.org/stable/c/156cac365e27a82b6…
https://git.kernel.org/stable/c/b14c5e04bd0f722ed…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 1b9845081633072c18f30d8cfd09c267adf0b109 , < 7d4eadee7042d27fcea659fcdd738f463a7d2e70 (git) Affected: 1b9845081633072c18f30d8cfd09c267adf0b109 , < 156cac365e27a82b64ae510c5f463fd81f0265b1 (git) Affected: 1b9845081633072c18f30d8cfd09c267adf0b109 , < b14c5e04bd0f722ed631845599d52d03fcae1bc1 (git)
Linux	Linux	Affected: 4.1 Unaffected: 0 , < 4.1 (semver) Unaffected: 6.18.14 , ≤ 6.18.* (semver) Unaffected: 6.19.4 , ≤ 6.19.* (semver) Unaffected: 7.0 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/btrfs/volumes.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "7d4eadee7042d27fcea659fcdd738f463a7d2e70",
              "status": "affected",
              "version": "1b9845081633072c18f30d8cfd09c267adf0b109",
              "versionType": "git"
            },
            {
              "lessThan": "156cac365e27a82b64ae510c5f463fd81f0265b1",
              "status": "affected",
              "version": "1b9845081633072c18f30d8cfd09c267adf0b109",
              "versionType": "git"
            },
            {
              "lessThan": "b14c5e04bd0f722ed631845599d52d03fcae1bc1",
              "status": "affected",
              "version": "1b9845081633072c18f30d8cfd09c267adf0b109",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/btrfs/volumes.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "4.1"
            },
            {
              "lessThan": "4.1",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.14",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.19.*",
              "status": "unaffected",
              "version": "6.19.4",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.0",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.14",
                  "versionStartIncluding": "4.1",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.19.4",
                  "versionStartIncluding": "4.1",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0",
                  "versionStartIncluding": "4.1",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix EEXIST abort due to non-consecutive gaps in chunk allocation\n\nI have been observing a number of systems aborting at\ninsert_dev_extents() in btrfs_create_pending_block_groups(). The\nfollowing is a sample stack trace of such an abort coming from forced\nchunk allocation (typically behind CONFIG_BTRFS_EXPERIMENTAL) but this\ncan theoretically happen to any DUP chunk allocation.\n\n  [81.801] ------------[ cut here ]------------\n  [81.801] BTRFS: Transaction aborted (error -17)\n  [81.801] WARNING: fs/btrfs/block-group.c:2876 at btrfs_create_pending_block_groups+0x721/0x770 [btrfs], CPU#1: bash/319\n  [81.802] Modules linked in: virtio_net btrfs xor zstd_compress raid6_pq null_blk\n  [81.803] CPU: 1 UID: 0 PID: 319 Comm: bash Kdump: loaded Not tainted 6.19.0-rc6+ #319 NONE\n  [81.803] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.17.0-2-2 04/01/2014\n  [81.804] RIP: 0010:btrfs_create_pending_block_groups+0x723/0x770 [btrfs]\n  [81.806] RSP: 0018:ffffa36241a6bce8 EFLAGS: 00010282\n  [81.806] RAX: 000000000000000d RBX: ffff8e699921e400 RCX: 0000000000000000\n  [81.807] RDX: 0000000002040001 RSI: 00000000ffffffef RDI: ffffffffc0608bf0\n  [81.807] RBP: 00000000ffffffef R08: ffff8e69830f6000 R09: 0000000000000007\n  [81.808] R10: ffff8e699921e5e8 R11: 0000000000000000 R12: ffff8e6999228000\n  [81.808] R13: ffff8e6984d82000 R14: ffff8e69966a69c0 R15: ffff8e69aa47b000\n  [81.809] FS:  00007fec6bdd9740(0000) GS:ffff8e6b1b379000(0000) knlGS:0000000000000000\n  [81.809] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  [81.810] CR2: 00005604833670f0 CR3: 0000000116679000 CR4: 00000000000006f0\n  [81.810] Call Trace:\n  [81.810]  \u003cTASK\u003e\n  [81.810]  __btrfs_end_transaction+0x3e/0x2b0 [btrfs]\n  [81.811]  btrfs_force_chunk_alloc_store+0xcd/0x140 [btrfs]\n  [81.811]  kernfs_fop_write_iter+0x15f/0x240\n  [81.812]  vfs_write+0x264/0x500\n  [81.812]  ksys_write+0x6c/0xe0\n  [81.812]  do_syscall_64+0x66/0x770\n  [81.812]  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  [81.813] RIP: 0033:0x7fec6be66197\n  [81.814] RSP: 002b:00007fffb159dd30 EFLAGS: 00000202 ORIG_RAX: 0000000000000001\n  [81.815] RAX: ffffffffffffffda RBX: 00007fec6bdd9740 RCX: 00007fec6be66197\n  [81.815] RDX: 0000000000000002 RSI: 0000560483374f80 RDI: 0000000000000001\n  [81.816] RBP: 0000560483374f80 R08: 0000000000000000 R09: 0000000000000000\n  [81.816] R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000002\n  [81.817] R13: 00007fec6bfb85c0 R14: 00007fec6bfb5ee0 R15: 00005604833729c0\n  [81.817]  \u003c/TASK\u003e\n  [81.817] irq event stamp: 20039\n  [81.818] hardirqs last  enabled at (20047): [\u003cffffffff99a68302\u003e] __up_console_sem+0x52/0x60\n  [81.818] hardirqs last disabled at (20056): [\u003cffffffff99a682e7\u003e] __up_console_sem+0x37/0x60\n  [81.819] softirqs last  enabled at (19470): [\u003cffffffff999d2b46\u003e] __irq_exit_rcu+0x96/0xc0\n  [81.819] softirqs last disabled at (19463): [\u003cffffffff999d2b46\u003e] __irq_exit_rcu+0x96/0xc0\n  [81.820] ---[ end trace 0000000000000000 ]---\n  [81.820] BTRFS: error (device dm-7 state A) in btrfs_create_pending_block_groups:2876: errno=-17 Object already exists\n\nInspecting these aborts with drgn, I observed a pattern of overlapping\nchunk_maps. Note how stripe 1 of the first chunk overlaps in physical\naddress with stripe 0 of the second chunk.\n\nPhysical Start     Physical End       Length       Logical            Type                 Stripe\n----------------------------------------------------------------------------------------------------\n0x0000000102500000 0x0000000142500000 1.0G         0x0000000641d00000 META|DUP             0/2\n0x0000000142500000 0x0000000182500000 1.0G         0x0000000641d00000 META|DUP             1/2\n0x0000000142500000 0x0000000182500000 1.0G         0x0000000601d00000 META|DUP             0/2\n0x0000000182500000 0x00000001c2500000 1.0G         0x0000000601d00000 META|DUP             1/2\n\nNow how could this possibly happen? All chunk allocation is\n---truncated---"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-27T12:17:51.905Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/7d4eadee7042d27fcea659fcdd738f463a7d2e70"
        },
        {
          "url": "https://git.kernel.org/stable/c/156cac365e27a82b64ae510c5f463fd81f0265b1"
        },
        {
          "url": "https://git.kernel.org/stable/c/b14c5e04bd0f722ed631845599d52d03fcae1bc1"
        }
      ],
      "title": "btrfs: fix EEXIST abort due to non-consecutive gaps in chunk allocation",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-45934",
    "datePublished": "2026-05-27T12:17:51.905Z",
    "dateReserved": "2026-05-13T15:03:33.086Z",
    "dateUpdated": "2026-05-27T12:17:51.905Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.