GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

CVE-2024-44975 (GCVE-0-2024-44975)

Vulnerability from cvelistv5 – Published: 2024-09-04 19:54 – Updated: 2026-05-11 20:33
VLAI
Title
cgroup/cpuset: fix panic caused by partcmd_update
Summary
In the Linux kernel, the following vulnerability has been resolved: cgroup/cpuset: fix panic caused by partcmd_update We find a bug as below: BUG: unable to handle page fault for address: 00000003 PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 3 PID: 358 Comm: bash Tainted: G W I 6.6.0-10893-g60d6 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/4 RIP: 0010:partition_sched_domains_locked+0x483/0x600 Code: 01 48 85 d2 74 0d 48 83 05 29 3f f8 03 01 f3 48 0f bc c2 89 c0 48 9 RSP: 0018:ffffc90000fdbc58 EFLAGS: 00000202 RAX: 0000000100000003 RBX: ffff888100b3dfa0 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000000002fe80 RBP: ffff888100b3dfb0 R08: 0000000000000001 R09: 0000000000000000 R10: ffffc90000fdbcb0 R11: 0000000000000004 R12: 0000000000000002 R13: ffff888100a92b48 R14: 0000000000000000 R15: 0000000000000000 FS: 00007f44a5425740(0000) GS:ffff888237d80000(0000) knlGS:0000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000100030973 CR3: 000000010722c000 CR4: 00000000000006e0 Call Trace: <TASK> ? show_regs+0x8c/0xa0 ? __die_body+0x23/0xa0 ? __die+0x3a/0x50 ? page_fault_oops+0x1d2/0x5c0 ? partition_sched_domains_locked+0x483/0x600 ? search_module_extables+0x2a/0xb0 ? search_exception_tables+0x67/0x90 ? kernelmode_fixup_or_oops+0x144/0x1b0 ? __bad_area_nosemaphore+0x211/0x360 ? up_read+0x3b/0x50 ? bad_area_nosemaphore+0x1a/0x30 ? exc_page_fault+0x890/0xd90 ? __lock_acquire.constprop.0+0x24f/0x8d0 ? __lock_acquire.constprop.0+0x24f/0x8d0 ? asm_exc_page_fault+0x26/0x30 ? partition_sched_domains_locked+0x483/0x600 ? partition_sched_domains_locked+0xf0/0x600 rebuild_sched_domains_locked+0x806/0xdc0 update_partition_sd_lb+0x118/0x130 cpuset_write_resmask+0xffc/0x1420 cgroup_file_write+0xb2/0x290 kernfs_fop_write_iter+0x194/0x290 new_sync_write+0xeb/0x160 vfs_write+0x16f/0x1d0 ksys_write+0x81/0x180 __x64_sys_write+0x21/0x30 x64_sys_call+0x2f25/0x4630 do_syscall_64+0x44/0xb0 entry_SYSCALL_64_after_hwframe+0x78/0xe2 RIP: 0033:0x7f44a553c887 It can be reproduced with cammands: cd /sys/fs/cgroup/ mkdir test cd test/ echo +cpuset > ../cgroup.subtree_control echo root > cpuset.cpus.partition cat /sys/fs/cgroup/cpuset.cpus.effective 0-3 echo 0-3 > cpuset.cpus // taking away all cpus from root This issue is caused by the incorrect rebuilding of scheduling domains. In this scenario, test/cpuset.cpus.partition should be an invalid root and should not trigger the rebuilding of scheduling domains. When calling update_parent_effective_cpumask with partcmd_update, if newmask is not null, it should recheck newmask whether there are cpus is available for parect/cs that has tasks.
Severity
No CVSS data available.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2024-09-10 15:26 UTC
Assigner
References
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 0c7f293efc87a06b51db9aa65256f8cb0a5a0a21 , < 73d6c6cf8ef6a3c532aa159f5114077746a372d6 (git)
Affected: 0c7f293efc87a06b51db9aa65256f8cb0a5a0a21 , < 959ab6350add903e352890af53e86663739fcb9a (git)
guessed Create a notification for this product.
Linux Linux Affected: 6.7
Unaffected: 0 , < 6.7 (semver)
Unaffected: 6.10.7 , ≤ 6.10.* (semver)
Unaffected: 6.11 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2024-44975",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-09-10T15:26:17.235376Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-09-12T17:33:03.893Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "kernel/cgroup/cpuset.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "73d6c6cf8ef6a3c532aa159f5114077746a372d6",
              "status": "affected",
              "version": "0c7f293efc87a06b51db9aa65256f8cb0a5a0a21",
              "versionType": "git"
            },
            {
              "lessThan": "959ab6350add903e352890af53e86663739fcb9a",
              "status": "affected",
              "version": "0c7f293efc87a06b51db9aa65256f8cb0a5a0a21",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "kernel/cgroup/cpuset.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.7"
            },
            {
              "lessThan": "6.7",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.10.*",
              "status": "unaffected",
              "version": "6.10.7",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.11",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.10.7",
                  "versionStartIncluding": "6.7",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.11",
                  "versionStartIncluding": "6.7",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncgroup/cpuset: fix panic caused by partcmd_update\n\nWe find a bug as below:\nBUG: unable to handle page fault for address: 00000003\nPGD 0 P4D 0\nOops: 0000 [#1] PREEMPT SMP NOPTI\nCPU: 3 PID: 358 Comm: bash Tainted: G        W I        6.6.0-10893-g60d6\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/4\nRIP: 0010:partition_sched_domains_locked+0x483/0x600\nCode: 01 48 85 d2 74 0d 48 83 05 29 3f f8 03 01 f3 48 0f bc c2 89 c0 48 9\nRSP: 0018:ffffc90000fdbc58 EFLAGS: 00000202\nRAX: 0000000100000003 RBX: ffff888100b3dfa0 RCX: 0000000000000000\nRDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000000002fe80\nRBP: ffff888100b3dfb0 R08: 0000000000000001 R09: 0000000000000000\nR10: ffffc90000fdbcb0 R11: 0000000000000004 R12: 0000000000000002\nR13: ffff888100a92b48 R14: 0000000000000000 R15: 0000000000000000\nFS:  00007f44a5425740(0000) GS:ffff888237d80000(0000) knlGS:0000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000100030973 CR3: 000000010722c000 CR4: 00000000000006e0\nCall Trace:\n \u003cTASK\u003e\n ? show_regs+0x8c/0xa0\n ? __die_body+0x23/0xa0\n ? __die+0x3a/0x50\n ? page_fault_oops+0x1d2/0x5c0\n ? partition_sched_domains_locked+0x483/0x600\n ? search_module_extables+0x2a/0xb0\n ? search_exception_tables+0x67/0x90\n ? kernelmode_fixup_or_oops+0x144/0x1b0\n ? __bad_area_nosemaphore+0x211/0x360\n ? up_read+0x3b/0x50\n ? bad_area_nosemaphore+0x1a/0x30\n ? exc_page_fault+0x890/0xd90\n ? __lock_acquire.constprop.0+0x24f/0x8d0\n ? __lock_acquire.constprop.0+0x24f/0x8d0\n ? asm_exc_page_fault+0x26/0x30\n ? partition_sched_domains_locked+0x483/0x600\n ? partition_sched_domains_locked+0xf0/0x600\n rebuild_sched_domains_locked+0x806/0xdc0\n update_partition_sd_lb+0x118/0x130\n cpuset_write_resmask+0xffc/0x1420\n cgroup_file_write+0xb2/0x290\n kernfs_fop_write_iter+0x194/0x290\n new_sync_write+0xeb/0x160\n vfs_write+0x16f/0x1d0\n ksys_write+0x81/0x180\n __x64_sys_write+0x21/0x30\n x64_sys_call+0x2f25/0x4630\n do_syscall_64+0x44/0xb0\n entry_SYSCALL_64_after_hwframe+0x78/0xe2\nRIP: 0033:0x7f44a553c887\n\nIt can be reproduced with cammands:\ncd /sys/fs/cgroup/\nmkdir test\ncd test/\necho +cpuset \u003e ../cgroup.subtree_control\necho root \u003e cpuset.cpus.partition\ncat /sys/fs/cgroup/cpuset.cpus.effective\n0-3\necho 0-3 \u003e cpuset.cpus // taking away all cpus from root\n\nThis issue is caused by the incorrect rebuilding of scheduling domains.\nIn this scenario, test/cpuset.cpus.partition should be an invalid root\nand should not trigger the rebuilding of scheduling domains. When calling\nupdate_parent_effective_cpumask with partcmd_update, if newmask is not\nnull, it should recheck newmask whether there are cpus is available\nfor parect/cs that has tasks."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-11T20:33:02.271Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/73d6c6cf8ef6a3c532aa159f5114077746a372d6"
        },
        {
          "url": "https://git.kernel.org/stable/c/959ab6350add903e352890af53e86663739fcb9a"
        }
      ],
      "title": "cgroup/cpuset: fix panic caused by partcmd_update",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-44975",
    "datePublished": "2024-09-04T19:54:27.622Z",
    "dateReserved": "2024-08-21T05:34:56.669Z",
    "dateUpdated": "2026-05-11T20:33:02.271Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2024-44975",
      "date": "2026-09-15",
      "epss": "0.00196",
      "percentile": "0.09538"
    },
    "fkie_nvd": {
      "configurations": "[{\"nodes\": [{\"operator\": \"OR\", \"negate\": false, \"cpeMatch\": [{\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"6.7\", \"versionEndExcluding\": \"6.10.7\", \"matchCriteriaId\": \"D2AFDFD1-D95A-4EB7-843B-5E7659518B67\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:6.11:rc1:*:*:*:*:*:*\", \"matchCriteriaId\": \"8B3CE743-2126-47A3-8B7C-822B502CF119\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:6.11:rc2:*:*:*:*:*:*\", \"matchCriteriaId\": \"4DEB27E7-30AA-45CC-8934-B89263EF3551\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:6.11:rc3:*:*:*:*:*:*\", \"matchCriteriaId\": \"E0005AEF-856E-47EB-BFE4-90C46899394D\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:6.11:rc4:*:*:*:*:*:*\", \"matchCriteriaId\": \"39889A68-6D34-47A6-82FC-CD0BF23D6754\"}]}]}]",
      "descriptions": "[{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\ncgroup/cpuset: fix panic caused by partcmd_update\\n\\nWe find a bug as below:\\nBUG: unable to handle page fault for address: 00000003\\nPGD 0 P4D 0\\nOops: 0000 [#1] PREEMPT SMP NOPTI\\nCPU: 3 PID: 358 Comm: bash Tainted: G        W I        6.6.0-10893-g60d6\\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/4\\nRIP: 0010:partition_sched_domains_locked+0x483/0x600\\nCode: 01 48 85 d2 74 0d 48 83 05 29 3f f8 03 01 f3 48 0f bc c2 89 c0 48 9\\nRSP: 0018:ffffc90000fdbc58 EFLAGS: 00000202\\nRAX: 0000000100000003 RBX: ffff888100b3dfa0 RCX: 0000000000000000\\nRDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000000002fe80\\nRBP: ffff888100b3dfb0 R08: 0000000000000001 R09: 0000000000000000\\nR10: ffffc90000fdbcb0 R11: 0000000000000004 R12: 0000000000000002\\nR13: ffff888100a92b48 R14: 0000000000000000 R15: 0000000000000000\\nFS:  00007f44a5425740(0000) GS:ffff888237d80000(0000) knlGS:0000000000000\\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\\nCR2: 0000000100030973 CR3: 000000010722c000 CR4: 00000000000006e0\\nCall Trace:\\n \u003cTASK\u003e\\n ? show_regs+0x8c/0xa0\\n ? __die_body+0x23/0xa0\\n ? __die+0x3a/0x50\\n ? page_fault_oops+0x1d2/0x5c0\\n ? partition_sched_domains_locked+0x483/0x600\\n ? search_module_extables+0x2a/0xb0\\n ? search_exception_tables+0x67/0x90\\n ? kernelmode_fixup_or_oops+0x144/0x1b0\\n ? __bad_area_nosemaphore+0x211/0x360\\n ? up_read+0x3b/0x50\\n ? bad_area_nosemaphore+0x1a/0x30\\n ? exc_page_fault+0x890/0xd90\\n ? __lock_acquire.constprop.0+0x24f/0x8d0\\n ? __lock_acquire.constprop.0+0x24f/0x8d0\\n ? asm_exc_page_fault+0x26/0x30\\n ? partition_sched_domains_locked+0x483/0x600\\n ? partition_sched_domains_locked+0xf0/0x600\\n rebuild_sched_domains_locked+0x806/0xdc0\\n update_partition_sd_lb+0x118/0x130\\n cpuset_write_resmask+0xffc/0x1420\\n cgroup_file_write+0xb2/0x290\\n kernfs_fop_write_iter+0x194/0x290\\n new_sync_write+0xeb/0x160\\n vfs_write+0x16f/0x1d0\\n ksys_write+0x81/0x180\\n __x64_sys_write+0x21/0x30\\n x64_sys_call+0x2f25/0x4630\\n do_syscall_64+0x44/0xb0\\n entry_SYSCALL_64_after_hwframe+0x78/0xe2\\nRIP: 0033:0x7f44a553c887\\n\\nIt can be reproduced with cammands:\\ncd /sys/fs/cgroup/\\nmkdir test\\ncd test/\\necho +cpuset \u003e ../cgroup.subtree_control\\necho root \u003e cpuset.cpus.partition\\ncat /sys/fs/cgroup/cpuset.cpus.effective\\n0-3\\necho 0-3 \u003e cpuset.cpus // taking away all cpus from root\\n\\nThis issue is caused by the incorrect rebuilding of scheduling domains.\\nIn this scenario, test/cpuset.cpus.partition should be an invalid root\\nand should not trigger the rebuilding of scheduling domains. When calling\\nupdate_parent_effective_cpumask with partcmd_update, if newmask is not\\nnull, it should recheck newmask whether there are cpus is available\\nfor parect/cs that has tasks.\"}, {\"lang\": \"es\", \"value\": \"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: cgroup/cpuset: arregla el p\\u00e1nico causado por partcmd_update Encontramos un error como el siguiente: ERROR: no se puede manejar el error de p\\u00e1gina para la direcci\\u00f3n: 00000003 PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 3 PID: 358 Comm: bash Tainted: GWI 6.6.0-10893-g60d6 Nombre del hardware: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/4 RIP: 0010:partition_sched_domains_locked+0x483/0x600 C\\u00f3digo: 01 48 85 d2 74 0d 48 83 05 29 3f f8 03 01 f3 48 0f bc c2 89 c0 48 9 RSP: 0018:ffffc90000fdbc58 EFLAGS: 00000202 RAX: 0000000100000003 RBX: ffff888100b3dfa0 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000002fe80 RBP: ffff888100b3dfb0 R08: 0000000000000001 R09: 0000000000000000 R10: ffffc90000fdbcb0 R11: 0000000000000004 R12: 0000000000000002 R13: ffff888100a92b48 R14: 0000000000000000 R15: 0000000000000000 FS: 00007f44a5425740(0000) GS:ffff888237d80000(0000) knlGS:0000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000100030973 CR3: 000000010722c000 CR4: 00000000000006e0 Seguimiento de llamadas:  ? show_regs+0x8c/0xa0 ? __die_body+0x23/0xa0 ? __die+0x3a/0x50 ? page_fault_oops+0x1d2/0x5c0 ? particion_sched_domains_locked+0x483/0x600 ? search_module_extables+0x2a/0xb0 ? search_exception_tables+0x67/0x90 ? kernelmode_fixup_or_oops+0x144/0x1b0 ? __bad_area_nosemaphore+0x211/0x360 ? up_read+0x3b/0x50 ? sem\\u00e1foro de nariz de \\u00e1rea defectuosa+0x1a/0x30 ? exc_page_fault+0x890/0xd90 ? __lock_acquire.constprop.0+0x24f/0x8d0 ? __lock_acquire.constprop.0+0x24f/0x8d0 ? asm_exc_page_fault+0x26/0x30 ? dominios programados de partici\\u00f3n bloqueados+0x483/0x600 ? partici\\u00f3n_sched_dominios_bloqueados+0xf0/0x600 reconstruir_sched_dominios_bloqueados+0x806/0xdc0 actualizar_partici\\u00f3n_sd_lb+0x118/0x130 resmask_escritura_cpuset+0xffc/0x1420 escritura_archivo_cgroup+0xb2/0x290 iterador_escritura_fop_kernfs+0x194/0x290 nueva_escritura_sincronizada+0xeb/0x160 escritura_vfs+0x16f/0x1d0 escritura_ksys+0x81/0x180 escritura_sys___x64+0x21/0x30 llamada_sys_x64+0x2f25/0x4630 llamada_sys_64+0x44/0xb0 entry_SYSCALL_64_after_hwframe+0x78/0xe2 RIP: 0033:0x7f44a553c887 Se puede reproducir con los siguientes comandos: cd /sys/fs/cgroup/ mkdir test cd test/ echo +cpuset \u0026gt; ../cgroup.subtree_control echo root \u0026gt; cpuset.cpus.partition cat /sys/fs/cgroup/cpuset.cpus.effective 0-3 echo 0-3 \u0026gt; cpuset.cpus // quitar todas las CPU de la ra\\u00edz Este problema se debe a la reconstrucci\\u00f3n incorrecta de los dominios de programaci\\u00f3n. En este escenario, test/cpuset.cpus.partition deber\\u00eda ser una ra\\u00edz no v\\u00e1lida y no deber\\u00eda activar la reconstrucci\\u00f3n de los dominios de programaci\\u00f3n. Al llamar a update_parent_effective_cpumask con partcmd_update, si newmask no es nulo, debe volver a verificar si newmask tiene CPU disponibles para parect/cs que tiene tareas.\"}]",
      "id": "CVE-2024-44975",
      "lastModified": "2024-10-03T14:32:31.677",
      "metrics": "{\"cvssMetricV31\": [{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"cvssData\": {\"version\": \"3.1\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\", \"baseScore\": 5.5, \"baseSeverity\": \"MEDIUM\", \"attackVector\": \"LOCAL\", \"attackComplexity\": \"LOW\", \"privilegesRequired\": \"LOW\", \"userInteraction\": \"NONE\", \"scope\": \"UNCHANGED\", \"confidentialityImpact\": \"NONE\", \"integrityImpact\": \"NONE\", \"availabilityImpact\": \"HIGH\"}, \"exploitabilityScore\": 1.8, \"impactScore\": 3.6}]}",
      "published": "2024-09-04T20:15:07.160",
      "references": "[{\"url\": \"https://git.kernel.org/stable/c/73d6c6cf8ef6a3c532aa159f5114077746a372d6\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/959ab6350add903e352890af53e86663739fcb9a\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}]",
      "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "vulnStatus": "Analyzed",
      "weaknesses": "[{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"description\": [{\"lang\": \"en\", \"value\": \"NVD-CWE-noinfo\"}]}]"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-44975\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-09-04T20:15:07.160\",\"lastModified\":\"2026-06-17T07:53:20.423\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\ncgroup/cpuset: fix panic caused by partcmd_update\\n\\nWe find a bug as below:\\nBUG: unable to handle page fault for address: 00000003\\nPGD 0 P4D 0\\nOops: 0000 [#1] PREEMPT SMP NOPTI\\nCPU: 3 PID: 358 Comm: bash Tainted: G        W I        6.6.0-10893-g60d6\\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/4\\nRIP: 0010:partition_sched_domains_locked+0x483/0x600\\nCode: 01 48 85 d2 74 0d 48 83 05 29 3f f8 03 01 f3 48 0f bc c2 89 c0 48 9\\nRSP: 0018:ffffc90000fdbc58 EFLAGS: 00000202\\nRAX: 0000000100000003 RBX: ffff888100b3dfa0 RCX: 0000000000000000\\nRDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000000002fe80\\nRBP: ffff888100b3dfb0 R08: 0000000000000001 R09: 0000000000000000\\nR10: ffffc90000fdbcb0 R11: 0000000000000004 R12: 0000000000000002\\nR13: ffff888100a92b48 R14: 0000000000000000 R15: 0000000000000000\\nFS:  00007f44a5425740(0000) GS:ffff888237d80000(0000) knlGS:0000000000000\\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\\nCR2: 0000000100030973 CR3: 000000010722c000 CR4: 00000000000006e0\\nCall Trace:\\n \u003cTASK\u003e\\n ? show_regs+0x8c/0xa0\\n ? __die_body+0x23/0xa0\\n ? __die+0x3a/0x50\\n ? page_fault_oops+0x1d2/0x5c0\\n ? partition_sched_domains_locked+0x483/0x600\\n ? search_module_extables+0x2a/0xb0\\n ? search_exception_tables+0x67/0x90\\n ? kernelmode_fixup_or_oops+0x144/0x1b0\\n ? __bad_area_nosemaphore+0x211/0x360\\n ? up_read+0x3b/0x50\\n ? bad_area_nosemaphore+0x1a/0x30\\n ? exc_page_fault+0x890/0xd90\\n ? __lock_acquire.constprop.0+0x24f/0x8d0\\n ? __lock_acquire.constprop.0+0x24f/0x8d0\\n ? asm_exc_page_fault+0x26/0x30\\n ? partition_sched_domains_locked+0x483/0x600\\n ? partition_sched_domains_locked+0xf0/0x600\\n rebuild_sched_domains_locked+0x806/0xdc0\\n update_partition_sd_lb+0x118/0x130\\n cpuset_write_resmask+0xffc/0x1420\\n cgroup_file_write+0xb2/0x290\\n kernfs_fop_write_iter+0x194/0x290\\n new_sync_write+0xeb/0x160\\n vfs_write+0x16f/0x1d0\\n ksys_write+0x81/0x180\\n __x64_sys_write+0x21/0x30\\n x64_sys_call+0x2f25/0x4630\\n do_syscall_64+0x44/0xb0\\n entry_SYSCALL_64_after_hwframe+0x78/0xe2\\nRIP: 0033:0x7f44a553c887\\n\\nIt can be reproduced with cammands:\\ncd /sys/fs/cgroup/\\nmkdir test\\ncd test/\\necho +cpuset \u003e ../cgroup.subtree_control\\necho root \u003e cpuset.cpus.partition\\ncat /sys/fs/cgroup/cpuset.cpus.effective\\n0-3\\necho 0-3 \u003e cpuset.cpus // taking away all cpus from root\\n\\nThis issue is caused by the incorrect rebuilding of scheduling domains.\\nIn this scenario, test/cpuset.cpus.partition should be an invalid root\\nand should not trigger the rebuilding of scheduling domains. When calling\\nupdate_parent_effective_cpumask with partcmd_update, if newmask is not\\nnull, it should recheck newmask whether there are cpus is available\\nfor parect/cs that has tasks.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: cgroup/cpuset: arregla el p\u00e1nico causado por partcmd_update Encontramos un error como el siguiente: ERROR: no se puede manejar el error de p\u00e1gina para la direcci\u00f3n: 00000003 PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 3 PID: 358 Comm: bash Tainted: GWI 6.6.0-10893-g60d6 Nombre del hardware: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/4 RIP: 0010:partition_sched_domains_locked+0x483/0x600 C\u00f3digo: 01 48 85 d2 74 0d 48 83 05 29 3f f8 03 01 f3 48 0f bc c2 89 c0 48 9 RSP: 0018:ffffc90000fdbc58 EFLAGS: 00000202 RAX: 0000000100000003 RBX: ffff888100b3dfa0 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000002fe80 RBP: ffff888100b3dfb0 R08: 0000000000000001 R09: 0000000000000000 R10: ffffc90000fdbcb0 R11: 0000000000000004 R12: 0000000000000002 R13: ffff888100a92b48 R14: 0000000000000000 R15: 0000000000000000 FS: 00007f44a5425740(0000) GS:ffff888237d80000(0000) knlGS:0000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000100030973 CR3: 000000010722c000 CR4: 00000000000006e0 Seguimiento de llamadas:  ? show_regs+0x8c/0xa0 ? __die_body+0x23/0xa0 ? __die+0x3a/0x50 ? page_fault_oops+0x1d2/0x5c0 ? particion_sched_domains_locked+0x483/0x600 ? search_module_extables+0x2a/0xb0 ? search_exception_tables+0x67/0x90 ? kernelmode_fixup_or_oops+0x144/0x1b0 ? __bad_area_nosemaphore+0x211/0x360 ? up_read+0x3b/0x50 ? sem\u00e1foro de nariz de \u00e1rea defectuosa+0x1a/0x30 ? exc_page_fault+0x890/0xd90 ? __lock_acquire.constprop.0+0x24f/0x8d0 ? __lock_acquire.constprop.0+0x24f/0x8d0 ? asm_exc_page_fault+0x26/0x30 ? dominios programados de partici\u00f3n bloqueados+0x483/0x600 ? partici\u00f3n_sched_dominios_bloqueados+0xf0/0x600 reconstruir_sched_dominios_bloqueados+0x806/0xdc0 actualizar_partici\u00f3n_sd_lb+0x118/0x130 resmask_escritura_cpuset+0xffc/0x1420 escritura_archivo_cgroup+0xb2/0x290 iterador_escritura_fop_kernfs+0x194/0x290 nueva_escritura_sincronizada+0xeb/0x160 escritura_vfs+0x16f/0x1d0 escritura_ksys+0x81/0x180 escritura_sys___x64+0x21/0x30 llamada_sys_x64+0x2f25/0x4630 llamada_sys_64+0x44/0xb0 entry_SYSCALL_64_after_hwframe+0x78/0xe2 RIP: 0033:0x7f44a553c887 Se puede reproducir con los siguientes comandos: cd /sys/fs/cgroup/ mkdir test cd test/ echo +cpuset \u0026gt; ../cgroup.subtree_control echo root \u0026gt; cpuset.cpus.partition cat /sys/fs/cgroup/cpuset.cpus.effective 0-3 echo 0-3 \u0026gt; cpuset.cpus // quitar todas las CPU de la ra\u00edz Este problema se debe a la reconstrucci\u00f3n incorrecta de los dominios de programaci\u00f3n. En este escenario, test/cpuset.cpus.partition deber\u00eda ser una ra\u00edz no v\u00e1lida y no deber\u00eda activar la reconstrucci\u00f3n de los dominios de programaci\u00f3n. Al llamar a update_parent_effective_cpumask con partcmd_update, si newmask no es nulo, debe volver a verificar si newmask tiene CPU disponibles para parect/cs que tiene tareas.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"kernel/cgroup/cpuset.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"0c7f293efc87a06b51db9aa65256f8cb0a5a0a21\",\"lessThan\":\"73d6c6cf8ef6a3c532aa159f5114077746a372d6\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"0c7f293efc87a06b51db9aa65256f8cb0a5a0a21\",\"lessThan\":\"959ab6350add903e352890af53e86663739fcb9a\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"kernel/cgroup/cpuset.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"6.7\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"6.7\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.10.7\",\"lessThanOrEqual\":\"6.10.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.11\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":3.6}],\"ssvcV203\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"ssvcData\":{\"timestamp\":\"2024-09-10T15:26:17.235376Z\",\"id\":\"CVE-2024-44975\",\"options\":[{\"exploitation\":\"none\"},{\"automatable\":\"no\"},{\"technicalImpact\":\"partial\"}],\"role\":\"CISA Coordinator\",\"version\":\"2.0.3\"}}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"NVD-CWE-noinfo\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.7\",\"versionEndExcluding\":\"6.10.7\",\"matchCriteriaId\":\"D2AFDFD1-D95A-4EB7-843B-5E7659518B67\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.11:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"8B3CE743-2126-47A3-8B7C-822B502CF119\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.11:rc2:*:*:*:*:*:*\",\"matchCriteriaId\":\"4DEB27E7-30AA-45CC-8934-B89263EF3551\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.11:rc3:*:*:*:*:*:*\",\"matchCriteriaId\":\"E0005AEF-856E-47EB-BFE4-90C46899394D\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.11:rc4:*:*:*:*:*:*\",\"matchCriteriaId\":\"39889A68-6D34-47A6-82FC-CD0BF23D6754\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/73d6c6cf8ef6a3c532aa159f5114077746a372d6\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/959ab6350add903e352890af53e86663739fcb9a\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}",
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-06-28T08:00:23+00:00",
      "cve": "CVE-2024-44975",
      "id": "CVE-2024-44975",
      "initial_release_date": "2024-09-04T00:00:00+00:00",
      "product_status:fixed": "305",
      "product_status:known_affected": "22",
      "product_status:known_not_affected": "90",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: cgroup/cpuset: fix panic caused by partcmd_update",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-44975.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-09-11T02:14:04Z",
      "cve": "CVE-2024-44975",
      "id": "CVE-2024-44975",
      "initial_release_date": "2024-09-05T02:46:52Z",
      "product_status:known_not_affected": "399",
      "product_status:recommended": "90",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2024-44975",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2024-44975.json",
      "version": "26"
    },
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-44975\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-09-10T15:26:17.235376Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-09-11T12:42:13.818Z\"}}], \"cna\": {\"title\": \"cgroup/cpuset: fix panic caused by partcmd_update\", \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"0c7f293efc87a06b51db9aa65256f8cb0a5a0a21\", \"lessThan\": \"73d6c6cf8ef6a3c532aa159f5114077746a372d6\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"0c7f293efc87a06b51db9aa65256f8cb0a5a0a21\", \"lessThan\": \"959ab6350add903e352890af53e86663739fcb9a\", \"versionType\": \"git\"}], \"programFiles\": [\"kernel/cgroup/cpuset.c\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"6.7\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"6.7\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"6.10.7\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.10.*\"}, {\"status\": \"unaffected\", \"version\": \"6.11\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"kernel/cgroup/cpuset.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/73d6c6cf8ef6a3c532aa159f5114077746a372d6\"}, {\"url\": \"https://git.kernel.org/stable/c/959ab6350add903e352890af53e86663739fcb9a\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\ncgroup/cpuset: fix panic caused by partcmd_update\\n\\nWe find a bug as below:\\nBUG: unable to handle page fault for address: 00000003\\nPGD 0 P4D 0\\nOops: 0000 [#1] PREEMPT SMP NOPTI\\nCPU: 3 PID: 358 Comm: bash Tainted: G        W I        6.6.0-10893-g60d6\\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/4\\nRIP: 0010:partition_sched_domains_locked+0x483/0x600\\nCode: 01 48 85 d2 74 0d 48 83 05 29 3f f8 03 01 f3 48 0f bc c2 89 c0 48 9\\nRSP: 0018:ffffc90000fdbc58 EFLAGS: 00000202\\nRAX: 0000000100000003 RBX: ffff888100b3dfa0 RCX: 0000000000000000\\nRDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000000002fe80\\nRBP: ffff888100b3dfb0 R08: 0000000000000001 R09: 0000000000000000\\nR10: ffffc90000fdbcb0 R11: 0000000000000004 R12: 0000000000000002\\nR13: ffff888100a92b48 R14: 0000000000000000 R15: 0000000000000000\\nFS:  00007f44a5425740(0000) GS:ffff888237d80000(0000) knlGS:0000000000000\\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\\nCR2: 0000000100030973 CR3: 000000010722c000 CR4: 00000000000006e0\\nCall Trace:\\n \u003cTASK\u003e\\n ? show_regs+0x8c/0xa0\\n ? __die_body+0x23/0xa0\\n ? __die+0x3a/0x50\\n ? page_fault_oops+0x1d2/0x5c0\\n ? partition_sched_domains_locked+0x483/0x600\\n ? search_module_extables+0x2a/0xb0\\n ? search_exception_tables+0x67/0x90\\n ? kernelmode_fixup_or_oops+0x144/0x1b0\\n ? __bad_area_nosemaphore+0x211/0x360\\n ? up_read+0x3b/0x50\\n ? bad_area_nosemaphore+0x1a/0x30\\n ? exc_page_fault+0x890/0xd90\\n ? __lock_acquire.constprop.0+0x24f/0x8d0\\n ? __lock_acquire.constprop.0+0x24f/0x8d0\\n ? asm_exc_page_fault+0x26/0x30\\n ? partition_sched_domains_locked+0x483/0x600\\n ? partition_sched_domains_locked+0xf0/0x600\\n rebuild_sched_domains_locked+0x806/0xdc0\\n update_partition_sd_lb+0x118/0x130\\n cpuset_write_resmask+0xffc/0x1420\\n cgroup_file_write+0xb2/0x290\\n kernfs_fop_write_iter+0x194/0x290\\n new_sync_write+0xeb/0x160\\n vfs_write+0x16f/0x1d0\\n ksys_write+0x81/0x180\\n __x64_sys_write+0x21/0x30\\n x64_sys_call+0x2f25/0x4630\\n do_syscall_64+0x44/0xb0\\n entry_SYSCALL_64_after_hwframe+0x78/0xe2\\nRIP: 0033:0x7f44a553c887\\n\\nIt can be reproduced with cammands:\\ncd /sys/fs/cgroup/\\nmkdir test\\ncd test/\\necho +cpuset \u003e ../cgroup.subtree_control\\necho root \u003e cpuset.cpus.partition\\ncat /sys/fs/cgroup/cpuset.cpus.effective\\n0-3\\necho 0-3 \u003e cpuset.cpus // taking away all cpus from root\\n\\nThis issue is caused by the incorrect rebuilding of scheduling domains.\\nIn this scenario, test/cpuset.cpus.partition should be an invalid root\\nand should not trigger the rebuilding of scheduling domains. When calling\\nupdate_parent_effective_cpumask with partcmd_update, if newmask is not\\nnull, it should recheck newmask whether there are cpus is available\\nfor parect/cs that has tasks.\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.10.7\", \"versionStartIncluding\": \"6.7\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.11\", \"versionStartIncluding\": \"6.7\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-05-11T20:33:02.271Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2024-44975\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-05-11T20:33:02.271Z\", \"dateReserved\": \"2024-08-21T05:34:56.669Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-09-04T19:54:27.622Z\", \"assignerShortName\": \"Linux\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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.


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.