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

CVE-2024-26725 (GCVE-0-2024-26725)

Vulnerability from cvelistv5 – Published: 2024-04-03 14:55 – Updated: 2026-05-11 20:02
VLAI
Title
dpll: fix possible deadlock during netlink dump operation
Summary
In the Linux kernel, the following vulnerability has been resolved: dpll: fix possible deadlock during netlink dump operation Recently, I've been hitting following deadlock warning during dpll pin dump: [52804.637962] ====================================================== [52804.638536] WARNING: possible circular locking dependency detected [52804.639111] 6.8.0-rc2jiri+ #1 Not tainted [52804.639529] ------------------------------------------------------ [52804.640104] python3/2984 is trying to acquire lock: [52804.640581] ffff88810e642678 (nlk_cb_mutex-GENERIC){+.+.}-{3:3}, at: netlink_dump+0xb3/0x780 [52804.641417] but task is already holding lock: [52804.642010] ffffffff83bde4c8 (dpll_lock){+.+.}-{3:3}, at: dpll_lock_dumpit+0x13/0x20 [52804.642747] which lock already depends on the new lock. [52804.643551] the existing dependency chain (in reverse order) is: [52804.644259] -> #1 (dpll_lock){+.+.}-{3:3}: [52804.644836] lock_acquire+0x174/0x3e0 [52804.645271] __mutex_lock+0x119/0x1150 [52804.645723] dpll_lock_dumpit+0x13/0x20 [52804.646169] genl_start+0x266/0x320 [52804.646578] __netlink_dump_start+0x321/0x450 [52804.647056] genl_family_rcv_msg_dumpit+0x155/0x1e0 [52804.647575] genl_rcv_msg+0x1ed/0x3b0 [52804.648001] netlink_rcv_skb+0xdc/0x210 [52804.648440] genl_rcv+0x24/0x40 [52804.648831] netlink_unicast+0x2f1/0x490 [52804.649290] netlink_sendmsg+0x36d/0x660 [52804.649742] __sock_sendmsg+0x73/0xc0 [52804.650165] __sys_sendto+0x184/0x210 [52804.650597] __x64_sys_sendto+0x72/0x80 [52804.651045] do_syscall_64+0x6f/0x140 [52804.651474] entry_SYSCALL_64_after_hwframe+0x46/0x4e [52804.652001] -> #0 (nlk_cb_mutex-GENERIC){+.+.}-{3:3}: [52804.652650] check_prev_add+0x1ae/0x1280 [52804.653107] __lock_acquire+0x1ed3/0x29a0 [52804.653559] lock_acquire+0x174/0x3e0 [52804.653984] __mutex_lock+0x119/0x1150 [52804.654423] netlink_dump+0xb3/0x780 [52804.654845] __netlink_dump_start+0x389/0x450 [52804.655321] genl_family_rcv_msg_dumpit+0x155/0x1e0 [52804.655842] genl_rcv_msg+0x1ed/0x3b0 [52804.656272] netlink_rcv_skb+0xdc/0x210 [52804.656721] genl_rcv+0x24/0x40 [52804.657119] netlink_unicast+0x2f1/0x490 [52804.657570] netlink_sendmsg+0x36d/0x660 [52804.658022] __sock_sendmsg+0x73/0xc0 [52804.658450] __sys_sendto+0x184/0x210 [52804.658877] __x64_sys_sendto+0x72/0x80 [52804.659322] do_syscall_64+0x6f/0x140 [52804.659752] entry_SYSCALL_64_after_hwframe+0x46/0x4e [52804.660281] other info that might help us debug this: [52804.661077] Possible unsafe locking scenario: [52804.661671] CPU0 CPU1 [52804.662129] ---- ---- [52804.662577] lock(dpll_lock); [52804.662924] lock(nlk_cb_mutex-GENERIC); [52804.663538] lock(dpll_lock); [52804.664073] lock(nlk_cb_mutex-GENERIC); [52804.664490] The issue as follows: __netlink_dump_start() calls control->start(cb) with nlk->cb_mutex held. In control->start(cb) the dpll_lock is taken. Then nlk->cb_mutex is released and taken again in netlink_dump(), while dpll_lock still being held. That leads to ABBA deadlock when another CPU races with the same operation. Fix this by moving dpll_lock taking into dumpit() callback which ensures correct lock taking order.
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:52 UTC
Assigner
References
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 9d71b54b65b1fb6c0d3a6c5c88ba9b915c783fbc , < 087739cbd0d0b87b6cec2c0799436ac66e24acc8 (git)
Affected: 9d71b54b65b1fb6c0d3a6c5c88ba9b915c783fbc , < 53c0441dd2c44ee93fddb5473885fd41e4bc2361 (git)
guessed Create a notification for this product.
Linux Linux Affected: 6.7
Unaffected: 0 , < 6.7 (semver)
Unaffected: 6.7.6 , ≤ 6.7.* (semver)
Unaffected: 6.8 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-02T00:14:12.969Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/087739cbd0d0b87b6cec2c0799436ac66e24acc8"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/53c0441dd2c44ee93fddb5473885fd41e4bc2361"
          }
        ],
        "title": "CVE Program Container"
      },
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2024-26725",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-09-10T15:52:13.550439Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-09-11T17:32:52.134Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "Documentation/netlink/specs/dpll.yaml",
            "drivers/dpll/dpll_netlink.c",
            "drivers/dpll/dpll_nl.c",
            "drivers/dpll/dpll_nl.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "087739cbd0d0b87b6cec2c0799436ac66e24acc8",
              "status": "affected",
              "version": "9d71b54b65b1fb6c0d3a6c5c88ba9b915c783fbc",
              "versionType": "git"
            },
            {
              "lessThan": "53c0441dd2c44ee93fddb5473885fd41e4bc2361",
              "status": "affected",
              "version": "9d71b54b65b1fb6c0d3a6c5c88ba9b915c783fbc",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "Documentation/netlink/specs/dpll.yaml",
            "drivers/dpll/dpll_netlink.c",
            "drivers/dpll/dpll_nl.c",
            "drivers/dpll/dpll_nl.h"
          ],
          "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.7.*",
              "status": "unaffected",
              "version": "6.7.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.8",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.7.6",
                  "versionStartIncluding": "6.7",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.8",
                  "versionStartIncluding": "6.7",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndpll: fix possible deadlock during netlink dump operation\n\nRecently, I\u0027ve been hitting following deadlock warning during dpll pin\ndump:\n\n[52804.637962] ======================================================\n[52804.638536] WARNING: possible circular locking dependency detected\n[52804.639111] 6.8.0-rc2jiri+ #1 Not tainted\n[52804.639529] ------------------------------------------------------\n[52804.640104] python3/2984 is trying to acquire lock:\n[52804.640581] ffff88810e642678 (nlk_cb_mutex-GENERIC){+.+.}-{3:3}, at: netlink_dump+0xb3/0x780\n[52804.641417]\n               but task is already holding lock:\n[52804.642010] ffffffff83bde4c8 (dpll_lock){+.+.}-{3:3}, at: dpll_lock_dumpit+0x13/0x20\n[52804.642747]\n               which lock already depends on the new lock.\n\n[52804.643551]\n               the existing dependency chain (in reverse order) is:\n[52804.644259]\n               -\u003e #1 (dpll_lock){+.+.}-{3:3}:\n[52804.644836]        lock_acquire+0x174/0x3e0\n[52804.645271]        __mutex_lock+0x119/0x1150\n[52804.645723]        dpll_lock_dumpit+0x13/0x20\n[52804.646169]        genl_start+0x266/0x320\n[52804.646578]        __netlink_dump_start+0x321/0x450\n[52804.647056]        genl_family_rcv_msg_dumpit+0x155/0x1e0\n[52804.647575]        genl_rcv_msg+0x1ed/0x3b0\n[52804.648001]        netlink_rcv_skb+0xdc/0x210\n[52804.648440]        genl_rcv+0x24/0x40\n[52804.648831]        netlink_unicast+0x2f1/0x490\n[52804.649290]        netlink_sendmsg+0x36d/0x660\n[52804.649742]        __sock_sendmsg+0x73/0xc0\n[52804.650165]        __sys_sendto+0x184/0x210\n[52804.650597]        __x64_sys_sendto+0x72/0x80\n[52804.651045]        do_syscall_64+0x6f/0x140\n[52804.651474]        entry_SYSCALL_64_after_hwframe+0x46/0x4e\n[52804.652001]\n               -\u003e #0 (nlk_cb_mutex-GENERIC){+.+.}-{3:3}:\n[52804.652650]        check_prev_add+0x1ae/0x1280\n[52804.653107]        __lock_acquire+0x1ed3/0x29a0\n[52804.653559]        lock_acquire+0x174/0x3e0\n[52804.653984]        __mutex_lock+0x119/0x1150\n[52804.654423]        netlink_dump+0xb3/0x780\n[52804.654845]        __netlink_dump_start+0x389/0x450\n[52804.655321]        genl_family_rcv_msg_dumpit+0x155/0x1e0\n[52804.655842]        genl_rcv_msg+0x1ed/0x3b0\n[52804.656272]        netlink_rcv_skb+0xdc/0x210\n[52804.656721]        genl_rcv+0x24/0x40\n[52804.657119]        netlink_unicast+0x2f1/0x490\n[52804.657570]        netlink_sendmsg+0x36d/0x660\n[52804.658022]        __sock_sendmsg+0x73/0xc0\n[52804.658450]        __sys_sendto+0x184/0x210\n[52804.658877]        __x64_sys_sendto+0x72/0x80\n[52804.659322]        do_syscall_64+0x6f/0x140\n[52804.659752]        entry_SYSCALL_64_after_hwframe+0x46/0x4e\n[52804.660281]\n               other info that might help us debug this:\n\n[52804.661077]  Possible unsafe locking scenario:\n\n[52804.661671]        CPU0                    CPU1\n[52804.662129]        ----                    ----\n[52804.662577]   lock(dpll_lock);\n[52804.662924]                                lock(nlk_cb_mutex-GENERIC);\n[52804.663538]                                lock(dpll_lock);\n[52804.664073]   lock(nlk_cb_mutex-GENERIC);\n[52804.664490]\n\nThe issue as follows: __netlink_dump_start() calls control-\u003estart(cb)\nwith nlk-\u003ecb_mutex held. In control-\u003estart(cb) the dpll_lock is taken.\nThen nlk-\u003ecb_mutex is released and taken again in netlink_dump(), while\ndpll_lock still being held. That leads to ABBA deadlock when another\nCPU races with the same operation.\n\nFix this by moving dpll_lock taking into dumpit() callback which ensures\ncorrect lock taking order."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-11T20:02:56.186Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/087739cbd0d0b87b6cec2c0799436ac66e24acc8"
        },
        {
          "url": "https://git.kernel.org/stable/c/53c0441dd2c44ee93fddb5473885fd41e4bc2361"
        }
      ],
      "title": "dpll: fix possible deadlock during netlink dump operation",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-26725",
    "datePublished": "2024-04-03T14:55:24.074Z",
    "dateReserved": "2024-02-19T14:20:24.163Z",
    "dateUpdated": "2026-05-11T20:02:56.186Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2024-26725",
      "date": "2026-09-15",
      "epss": "0.0015",
      "percentile": "0.04529"
    },
    "fkie_nvd": {
      "configurations": "[{\"nodes\": [{\"operator\": \"OR\", \"negate\": false, \"cpeMatch\": [{\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"6.7\", \"versionEndExcluding\": \"6.7.6\", \"matchCriteriaId\": \"C6D6A5C8-7308-42A9-8A72-ABF3DEA4BB82\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:6.8:rc1:*:*:*:*:*:*\", \"matchCriteriaId\": \"B9F4EA73-0894-400F-A490-3A397AB7A517\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:6.8:rc2:*:*:*:*:*:*\", \"matchCriteriaId\": \"056BD938-0A27-4569-B391-30578B309EE3\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:6.8:rc3:*:*:*:*:*:*\", \"matchCriteriaId\": \"F02056A5-B362-4370-9FF8-6F0BD384D520\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:6.8:rc4:*:*:*:*:*:*\", \"matchCriteriaId\": \"62075ACE-B2A0-4B16-829D-B3DA5AE5CC41\"}]}]}]",
      "descriptions": "[{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\ndpll: fix possible deadlock during netlink dump operation\\n\\nRecently, I\u0027ve been hitting following deadlock warning during dpll pin\\ndump:\\n\\n[52804.637962] ======================================================\\n[52804.638536] WARNING: possible circular locking dependency detected\\n[52804.639111] 6.8.0-rc2jiri+ #1 Not tainted\\n[52804.639529] ------------------------------------------------------\\n[52804.640104] python3/2984 is trying to acquire lock:\\n[52804.640581] ffff88810e642678 (nlk_cb_mutex-GENERIC){+.+.}-{3:3}, at: netlink_dump+0xb3/0x780\\n[52804.641417]\\n               but task is already holding lock:\\n[52804.642010] ffffffff83bde4c8 (dpll_lock){+.+.}-{3:3}, at: dpll_lock_dumpit+0x13/0x20\\n[52804.642747]\\n               which lock already depends on the new lock.\\n\\n[52804.643551]\\n               the existing dependency chain (in reverse order) is:\\n[52804.644259]\\n               -\u003e #1 (dpll_lock){+.+.}-{3:3}:\\n[52804.644836]        lock_acquire+0x174/0x3e0\\n[52804.645271]        __mutex_lock+0x119/0x1150\\n[52804.645723]        dpll_lock_dumpit+0x13/0x20\\n[52804.646169]        genl_start+0x266/0x320\\n[52804.646578]        __netlink_dump_start+0x321/0x450\\n[52804.647056]        genl_family_rcv_msg_dumpit+0x155/0x1e0\\n[52804.647575]        genl_rcv_msg+0x1ed/0x3b0\\n[52804.648001]        netlink_rcv_skb+0xdc/0x210\\n[52804.648440]        genl_rcv+0x24/0x40\\n[52804.648831]        netlink_unicast+0x2f1/0x490\\n[52804.649290]        netlink_sendmsg+0x36d/0x660\\n[52804.649742]        __sock_sendmsg+0x73/0xc0\\n[52804.650165]        __sys_sendto+0x184/0x210\\n[52804.650597]        __x64_sys_sendto+0x72/0x80\\n[52804.651045]        do_syscall_64+0x6f/0x140\\n[52804.651474]        entry_SYSCALL_64_after_hwframe+0x46/0x4e\\n[52804.652001]\\n               -\u003e #0 (nlk_cb_mutex-GENERIC){+.+.}-{3:3}:\\n[52804.652650]        check_prev_add+0x1ae/0x1280\\n[52804.653107]        __lock_acquire+0x1ed3/0x29a0\\n[52804.653559]        lock_acquire+0x174/0x3e0\\n[52804.653984]        __mutex_lock+0x119/0x1150\\n[52804.654423]        netlink_dump+0xb3/0x780\\n[52804.654845]        __netlink_dump_start+0x389/0x450\\n[52804.655321]        genl_family_rcv_msg_dumpit+0x155/0x1e0\\n[52804.655842]        genl_rcv_msg+0x1ed/0x3b0\\n[52804.656272]        netlink_rcv_skb+0xdc/0x210\\n[52804.656721]        genl_rcv+0x24/0x40\\n[52804.657119]        netlink_unicast+0x2f1/0x490\\n[52804.657570]        netlink_sendmsg+0x36d/0x660\\n[52804.658022]        __sock_sendmsg+0x73/0xc0\\n[52804.658450]        __sys_sendto+0x184/0x210\\n[52804.658877]        __x64_sys_sendto+0x72/0x80\\n[52804.659322]        do_syscall_64+0x6f/0x140\\n[52804.659752]        entry_SYSCALL_64_after_hwframe+0x46/0x4e\\n[52804.660281]\\n               other info that might help us debug this:\\n\\n[52804.661077]  Possible unsafe locking scenario:\\n\\n[52804.661671]        CPU0                    CPU1\\n[52804.662129]        ----                    ----\\n[52804.662577]   lock(dpll_lock);\\n[52804.662924]                                lock(nlk_cb_mutex-GENERIC);\\n[52804.663538]                                lock(dpll_lock);\\n[52804.664073]   lock(nlk_cb_mutex-GENERIC);\\n[52804.664490]\\n\\nThe issue as follows: __netlink_dump_start() calls control-\u003estart(cb)\\nwith nlk-\u003ecb_mutex held. In control-\u003estart(cb) the dpll_lock is taken.\\nThen nlk-\u003ecb_mutex is released and taken again in netlink_dump(), while\\ndpll_lock still being held. That leads to ABBA deadlock when another\\nCPU races with the same operation.\\n\\nFix this by moving dpll_lock taking into dumpit() callback which ensures\\ncorrect lock taking order.\"}, {\"lang\": \"es\", \"value\": \"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: dpll: soluciona un posible punto muerto durante la operaci\\u00f3n de volcado de netlink Recientemente, he estado recibiendo la siguiente advertencia de punto muerto durante el volcado de pin de dpll: [52804.637962] =========== =========================================== [52804.638536] ADVERTENCIA: posible circular dependencia de bloqueo detectada [52804.639111] 6.8.0-rc2jiri+ #1 No contaminado [52804.639529] -------------------------------- ---------------------- [52804.640104] python3/2984 est\\u00e1 intentando adquirir el bloqueo: [52804.640581] ffff88810e642678 (nlk_cb_mutex-GENERIC){+.+.}- {3:3}, en: netlink_dump+0xb3/0x780 [52804.641417] pero la tarea ya mantiene el bloqueo: [52804.642010] ffffffff83bde4c8 (dpll_lock){+.+.}-{3:3}, en: dpll_lock_dumpit+0x13/0x20 [52804.642747] qu\\u00e9 bloqueo ya depende del nuevo bloqueo. [52804.643551] la cadena de dependencia existente (en orden inverso) es: [52804.644259] -\u0026gt; #1 (dpll_lock){+.+.}-{3:3}: [52804.644836] lock_acquire+0x174/0x3e0 [52804.645271] __mutex_lock+ 0x119/0x1150 [52804.645723] dpll_lock_dumpit+0x13/0x20 [52804.646169] genl_start+0x266/0x320 [52804.646578] __netlink_dump_start+0x321/0x450 [52804.647056 ] genl_family_rcv_msg_dumpit+0x155/0x1e0 [52804.647575] genl_rcv_msg+0x1ed/0x3b0 [52804.648001] netlink_rcv_skb+0xdc/ 0x210 [52804.648440] genl_rcv+0x24/0x40 [52804.648831] netlink_unicast+0x2f1/0x490 [52804.649290] netlink_sendmsg+0x36d/0x660 [52804.649742] __sock_sendmsg +0x73/0xc0 [52804.650165] __sys_sendto+0x184/0x210 [52804.650597] __x64_sys_sendto+0x72/0x80 [ 52804.651045] do_syscall_64+0x6f/0x140 [52804.651474] Entry_SYSCALL_64_after_hwframe+0x46/0x4e [52804.652001] -\u0026gt; #0 (nlk_cb_mutex-GENERIC){+.+.}-{3:3}: [52804.6 52650] check_prev_add+0x1ae/0x1280 [52804.653107 ] __lock_acquire+0x1ed3/0x29a0 [52804.653559] lock_acquire+0x174/0x3e0 [52804.653984] __mutex_lock+0x119/0x1150 [52804.654423] netlink_dump+0xb3/0x780 [52804.654 845] __netlink_dump_start+0x389/0x450 [52804.655321] genl_family_rcv_msg_dumpit+0x155/0x1e0 [52804.655842] genl_rcv_msg +0x1ed/0x3b0 [52804.656272] netlink_rcv_skb+0xdc/0x210 [52804.656721] genl_rcv+0x24/0x40 [52804.657119] netlink_unicast+0x2f1/0x490 [52804.657570] netlink_sendm sg+0x36d/0x660 [52804.658022] __sock_sendmsg+0x73/0xc0 [52804.658450] __sys_sendto+0x184 /0x210 [52804.658877] __x64_sys_sendto+0x72/0x80 [52804.659322] do_syscall_64+0x6f/0x140 [52804.659752] Entry_SYSCALL_64_after_hwframe+0x46/0x4e [52804.66 0281] otra informaci\\u00f3n que podr\\u00eda ayudarnos a depurar esto: [52804.661077] Posible escenario de bloqueo inseguro: [52804.661671] CPU0 CPU1 [52804.662129] ---- ---- [52804.662577] bloqueo(dpll_lock); [52804.662924] bloqueo (nlk_cb_mutex-GENERIC); [52804.663538] bloqueo(dpll_lock); [52804.664073] bloqueo (nlk_cb_mutex-GENERIC); [52804.664490] El problema es el siguiente: __netlink_dump_start() llama a control-\u0026gt;start(cb) con nlk-\u0026gt;cb_mutex retenido. En control-\u0026gt;start(cb) se toma dpll_lock. Luego, nlk-\u0026gt;cb_mutex se libera y se toma nuevamente en netlink_dump(), mientras dpll_lock a\\u00fan se mantiene. Eso lleva a un punto muerto de ABBA cuando otra CPU corre con la misma operaci\\u00f3n. Solucione este problema moviendo dpll_lock a la devoluci\\u00f3n de llamada dumpit(), lo que garantiza el orden correcto de toma de bloqueo.\"}]",
      "id": "CVE-2024-26725",
      "lastModified": "2025-01-07T17:28:15.293",
      "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-04-03T15:15:54.257",
      "references": "[{\"url\": \"https://git.kernel.org/stable/c/087739cbd0d0b87b6cec2c0799436ac66e24acc8\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/53c0441dd2c44ee93fddb5473885fd41e4bc2361\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/087739cbd0d0b87b6cec2c0799436ac66e24acc8\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/53c0441dd2c44ee93fddb5473885fd41e4bc2361\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\", \"tags\": [\"Patch\"]}]",
      "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "vulnStatus": "Analyzed",
      "weaknesses": "[{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-667\"}]}]"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-26725\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-04-03T15:15:54.257\",\"lastModified\":\"2026-06-17T07:18:11.083\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\ndpll: fix possible deadlock during netlink dump operation\\n\\nRecently, I\u0027ve been hitting following deadlock warning during dpll pin\\ndump:\\n\\n[52804.637962] ======================================================\\n[52804.638536] WARNING: possible circular locking dependency detected\\n[52804.639111] 6.8.0-rc2jiri+ #1 Not tainted\\n[52804.639529] ------------------------------------------------------\\n[52804.640104] python3/2984 is trying to acquire lock:\\n[52804.640581] ffff88810e642678 (nlk_cb_mutex-GENERIC){+.+.}-{3:3}, at: netlink_dump+0xb3/0x780\\n[52804.641417]\\n               but task is already holding lock:\\n[52804.642010] ffffffff83bde4c8 (dpll_lock){+.+.}-{3:3}, at: dpll_lock_dumpit+0x13/0x20\\n[52804.642747]\\n               which lock already depends on the new lock.\\n\\n[52804.643551]\\n               the existing dependency chain (in reverse order) is:\\n[52804.644259]\\n               -\u003e #1 (dpll_lock){+.+.}-{3:3}:\\n[52804.644836]        lock_acquire+0x174/0x3e0\\n[52804.645271]        __mutex_lock+0x119/0x1150\\n[52804.645723]        dpll_lock_dumpit+0x13/0x20\\n[52804.646169]        genl_start+0x266/0x320\\n[52804.646578]        __netlink_dump_start+0x321/0x450\\n[52804.647056]        genl_family_rcv_msg_dumpit+0x155/0x1e0\\n[52804.647575]        genl_rcv_msg+0x1ed/0x3b0\\n[52804.648001]        netlink_rcv_skb+0xdc/0x210\\n[52804.648440]        genl_rcv+0x24/0x40\\n[52804.648831]        netlink_unicast+0x2f1/0x490\\n[52804.649290]        netlink_sendmsg+0x36d/0x660\\n[52804.649742]        __sock_sendmsg+0x73/0xc0\\n[52804.650165]        __sys_sendto+0x184/0x210\\n[52804.650597]        __x64_sys_sendto+0x72/0x80\\n[52804.651045]        do_syscall_64+0x6f/0x140\\n[52804.651474]        entry_SYSCALL_64_after_hwframe+0x46/0x4e\\n[52804.652001]\\n               -\u003e #0 (nlk_cb_mutex-GENERIC){+.+.}-{3:3}:\\n[52804.652650]        check_prev_add+0x1ae/0x1280\\n[52804.653107]        __lock_acquire+0x1ed3/0x29a0\\n[52804.653559]        lock_acquire+0x174/0x3e0\\n[52804.653984]        __mutex_lock+0x119/0x1150\\n[52804.654423]        netlink_dump+0xb3/0x780\\n[52804.654845]        __netlink_dump_start+0x389/0x450\\n[52804.655321]        genl_family_rcv_msg_dumpit+0x155/0x1e0\\n[52804.655842]        genl_rcv_msg+0x1ed/0x3b0\\n[52804.656272]        netlink_rcv_skb+0xdc/0x210\\n[52804.656721]        genl_rcv+0x24/0x40\\n[52804.657119]        netlink_unicast+0x2f1/0x490\\n[52804.657570]        netlink_sendmsg+0x36d/0x660\\n[52804.658022]        __sock_sendmsg+0x73/0xc0\\n[52804.658450]        __sys_sendto+0x184/0x210\\n[52804.658877]        __x64_sys_sendto+0x72/0x80\\n[52804.659322]        do_syscall_64+0x6f/0x140\\n[52804.659752]        entry_SYSCALL_64_after_hwframe+0x46/0x4e\\n[52804.660281]\\n               other info that might help us debug this:\\n\\n[52804.661077]  Possible unsafe locking scenario:\\n\\n[52804.661671]        CPU0                    CPU1\\n[52804.662129]        ----                    ----\\n[52804.662577]   lock(dpll_lock);\\n[52804.662924]                                lock(nlk_cb_mutex-GENERIC);\\n[52804.663538]                                lock(dpll_lock);\\n[52804.664073]   lock(nlk_cb_mutex-GENERIC);\\n[52804.664490]\\n\\nThe issue as follows: __netlink_dump_start() calls control-\u003estart(cb)\\nwith nlk-\u003ecb_mutex held. In control-\u003estart(cb) the dpll_lock is taken.\\nThen nlk-\u003ecb_mutex is released and taken again in netlink_dump(), while\\ndpll_lock still being held. That leads to ABBA deadlock when another\\nCPU races with the same operation.\\n\\nFix this by moving dpll_lock taking into dumpit() callback which ensures\\ncorrect lock taking order.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: dpll: soluciona un posible punto muerto durante la operaci\u00f3n de volcado de netlink Recientemente, he estado recibiendo la siguiente advertencia de punto muerto durante el volcado de pin de dpll: [52804.637962] =========== =========================================== [52804.638536] ADVERTENCIA: posible circular dependencia de bloqueo detectada [52804.639111] 6.8.0-rc2jiri+ #1 No contaminado [52804.639529] -------------------------------- ---------------------- [52804.640104] python3/2984 est\u00e1 intentando adquirir el bloqueo: [52804.640581] ffff88810e642678 (nlk_cb_mutex-GENERIC){+.+.}- {3:3}, en: netlink_dump+0xb3/0x780 [52804.641417] pero la tarea ya mantiene el bloqueo: [52804.642010] ffffffff83bde4c8 (dpll_lock){+.+.}-{3:3}, en: dpll_lock_dumpit+0x13/0x20 [52804.642747] qu\u00e9 bloqueo ya depende del nuevo bloqueo. [52804.643551] la cadena de dependencia existente (en orden inverso) es: [52804.644259] -\u0026gt; #1 (dpll_lock){+.+.}-{3:3}: [52804.644836] lock_acquire+0x174/0x3e0 [52804.645271] __mutex_lock+ 0x119/0x1150 [52804.645723] dpll_lock_dumpit+0x13/0x20 [52804.646169] genl_start+0x266/0x320 [52804.646578] __netlink_dump_start+0x321/0x450 [52804.647056 ] genl_family_rcv_msg_dumpit+0x155/0x1e0 [52804.647575] genl_rcv_msg+0x1ed/0x3b0 [52804.648001] netlink_rcv_skb+0xdc/ 0x210 [52804.648440] genl_rcv+0x24/0x40 [52804.648831] netlink_unicast+0x2f1/0x490 [52804.649290] netlink_sendmsg+0x36d/0x660 [52804.649742] __sock_sendmsg +0x73/0xc0 [52804.650165] __sys_sendto+0x184/0x210 [52804.650597] __x64_sys_sendto+0x72/0x80 [ 52804.651045] do_syscall_64+0x6f/0x140 [52804.651474] Entry_SYSCALL_64_after_hwframe+0x46/0x4e [52804.652001] -\u0026gt; #0 (nlk_cb_mutex-GENERIC){+.+.}-{3:3}: [52804.6 52650] check_prev_add+0x1ae/0x1280 [52804.653107 ] __lock_acquire+0x1ed3/0x29a0 [52804.653559] lock_acquire+0x174/0x3e0 [52804.653984] __mutex_lock+0x119/0x1150 [52804.654423] netlink_dump+0xb3/0x780 [52804.654 845] __netlink_dump_start+0x389/0x450 [52804.655321] genl_family_rcv_msg_dumpit+0x155/0x1e0 [52804.655842] genl_rcv_msg +0x1ed/0x3b0 [52804.656272] netlink_rcv_skb+0xdc/0x210 [52804.656721] genl_rcv+0x24/0x40 [52804.657119] netlink_unicast+0x2f1/0x490 [52804.657570] netlink_sendm sg+0x36d/0x660 [52804.658022] __sock_sendmsg+0x73/0xc0 [52804.658450] __sys_sendto+0x184 /0x210 [52804.658877] __x64_sys_sendto+0x72/0x80 [52804.659322] do_syscall_64+0x6f/0x140 [52804.659752] Entry_SYSCALL_64_after_hwframe+0x46/0x4e [52804.66 0281] otra informaci\u00f3n que podr\u00eda ayudarnos a depurar esto: [52804.661077] Posible escenario de bloqueo inseguro: [52804.661671] CPU0 CPU1 [52804.662129] ---- ---- [52804.662577] bloqueo(dpll_lock); [52804.662924] bloqueo (nlk_cb_mutex-GENERIC); [52804.663538] bloqueo(dpll_lock); [52804.664073] bloqueo (nlk_cb_mutex-GENERIC); [52804.664490] El problema es el siguiente: __netlink_dump_start() llama a control-\u0026gt;start(cb) con nlk-\u0026gt;cb_mutex retenido. En control-\u0026gt;start(cb) se toma dpll_lock. Luego, nlk-\u0026gt;cb_mutex se libera y se toma nuevamente en netlink_dump(), mientras dpll_lock a\u00fan se mantiene. Eso lleva a un punto muerto de ABBA cuando otra CPU corre con la misma operaci\u00f3n. Solucione este problema moviendo dpll_lock a la devoluci\u00f3n de llamada dumpit(), lo que garantiza el orden correcto de toma de bloqueo.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"Documentation/netlink/specs/dpll.yaml\",\"drivers/dpll/dpll_netlink.c\",\"drivers/dpll/dpll_nl.c\",\"drivers/dpll/dpll_nl.h\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"9d71b54b65b1fb6c0d3a6c5c88ba9b915c783fbc\",\"lessThan\":\"087739cbd0d0b87b6cec2c0799436ac66e24acc8\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"9d71b54b65b1fb6c0d3a6c5c88ba9b915c783fbc\",\"lessThan\":\"53c0441dd2c44ee93fddb5473885fd41e4bc2361\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"Documentation/netlink/specs/dpll.yaml\",\"drivers/dpll/dpll_netlink.c\",\"drivers/dpll/dpll_nl.c\",\"drivers/dpll/dpll_nl.h\"],\"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.7.6\",\"lessThanOrEqual\":\"6.7.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.8\",\"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:52:13.550439Z\",\"id\":\"CVE-2024-26725\",\"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\":\"CWE-667\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.7\",\"versionEndExcluding\":\"6.7.6\",\"matchCriteriaId\":\"C6D6A5C8-7308-42A9-8A72-ABF3DEA4BB82\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.8:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"B9F4EA73-0894-400F-A490-3A397AB7A517\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.8:rc2:*:*:*:*:*:*\",\"matchCriteriaId\":\"056BD938-0A27-4569-B391-30578B309EE3\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.8:rc3:*:*:*:*:*:*\",\"matchCriteriaId\":\"F02056A5-B362-4370-9FF8-6F0BD384D520\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.8:rc4:*:*:*:*:*:*\",\"matchCriteriaId\":\"62075ACE-B2A0-4B16-829D-B3DA5AE5CC41\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/087739cbd0d0b87b6cec2c0799436ac66e24acc8\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/53c0441dd2c44ee93fddb5473885fd41e4bc2361\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/087739cbd0d0b87b6cec2c0799436ac66e24acc8\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/53c0441dd2c44ee93fddb5473885fd41e4bc2361\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\"]}]}}",
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-06-28T08:03:02+00:00",
      "cve": "CVE-2024-26725",
      "id": "CVE-2024-26725",
      "initial_release_date": "2024-04-03T00:00:00+00:00",
      "product_status:fixed": "280",
      "product_status:known_affected": "22",
      "product_status:known_not_affected": "98",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: dpll: fix possible deadlock during netlink dump operation",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-26725.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-09-03T00:26:44Z",
      "cve": "CVE-2024-26725",
      "id": "CVE-2024-26725",
      "initial_release_date": "2024-04-06T01:59:12Z",
      "product_status:known_not_affected": "362",
      "product_status:recommended": "202",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2024-26725",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2024-26725.json",
      "version": "36"
    },
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://git.kernel.org/stable/c/087739cbd0d0b87b6cec2c0799436ac66e24acc8\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/53c0441dd2c44ee93fddb5473885fd41e4bc2361\", \"tags\": [\"x_transferred\"]}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2024-08-02T00:14:12.969Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-26725\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-09-10T15:52:13.550439Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-09-11T12:42:13.156Z\"}}], \"cna\": {\"title\": \"dpll: fix possible deadlock during netlink dump operation\", \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"9d71b54b65b1fb6c0d3a6c5c88ba9b915c783fbc\", \"lessThan\": \"087739cbd0d0b87b6cec2c0799436ac66e24acc8\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"9d71b54b65b1fb6c0d3a6c5c88ba9b915c783fbc\", \"lessThan\": \"53c0441dd2c44ee93fddb5473885fd41e4bc2361\", \"versionType\": \"git\"}], \"programFiles\": [\"Documentation/netlink/specs/dpll.yaml\", \"drivers/dpll/dpll_netlink.c\", \"drivers/dpll/dpll_nl.c\", \"drivers/dpll/dpll_nl.h\"], \"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.7.6\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.7.*\"}, {\"status\": \"unaffected\", \"version\": \"6.8\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"Documentation/netlink/specs/dpll.yaml\", \"drivers/dpll/dpll_netlink.c\", \"drivers/dpll/dpll_nl.c\", \"drivers/dpll/dpll_nl.h\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/087739cbd0d0b87b6cec2c0799436ac66e24acc8\"}, {\"url\": \"https://git.kernel.org/stable/c/53c0441dd2c44ee93fddb5473885fd41e4bc2361\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\ndpll: fix possible deadlock during netlink dump operation\\n\\nRecently, I\u0027ve been hitting following deadlock warning during dpll pin\\ndump:\\n\\n[52804.637962] ======================================================\\n[52804.638536] WARNING: possible circular locking dependency detected\\n[52804.639111] 6.8.0-rc2jiri+ #1 Not tainted\\n[52804.639529] ------------------------------------------------------\\n[52804.640104] python3/2984 is trying to acquire lock:\\n[52804.640581] ffff88810e642678 (nlk_cb_mutex-GENERIC){+.+.}-{3:3}, at: netlink_dump+0xb3/0x780\\n[52804.641417]\\n               but task is already holding lock:\\n[52804.642010] ffffffff83bde4c8 (dpll_lock){+.+.}-{3:3}, at: dpll_lock_dumpit+0x13/0x20\\n[52804.642747]\\n               which lock already depends on the new lock.\\n\\n[52804.643551]\\n               the existing dependency chain (in reverse order) is:\\n[52804.644259]\\n               -\u003e #1 (dpll_lock){+.+.}-{3:3}:\\n[52804.644836]        lock_acquire+0x174/0x3e0\\n[52804.645271]        __mutex_lock+0x119/0x1150\\n[52804.645723]        dpll_lock_dumpit+0x13/0x20\\n[52804.646169]        genl_start+0x266/0x320\\n[52804.646578]        __netlink_dump_start+0x321/0x450\\n[52804.647056]        genl_family_rcv_msg_dumpit+0x155/0x1e0\\n[52804.647575]        genl_rcv_msg+0x1ed/0x3b0\\n[52804.648001]        netlink_rcv_skb+0xdc/0x210\\n[52804.648440]        genl_rcv+0x24/0x40\\n[52804.648831]        netlink_unicast+0x2f1/0x490\\n[52804.649290]        netlink_sendmsg+0x36d/0x660\\n[52804.649742]        __sock_sendmsg+0x73/0xc0\\n[52804.650165]        __sys_sendto+0x184/0x210\\n[52804.650597]        __x64_sys_sendto+0x72/0x80\\n[52804.651045]        do_syscall_64+0x6f/0x140\\n[52804.651474]        entry_SYSCALL_64_after_hwframe+0x46/0x4e\\n[52804.652001]\\n               -\u003e #0 (nlk_cb_mutex-GENERIC){+.+.}-{3:3}:\\n[52804.652650]        check_prev_add+0x1ae/0x1280\\n[52804.653107]        __lock_acquire+0x1ed3/0x29a0\\n[52804.653559]        lock_acquire+0x174/0x3e0\\n[52804.653984]        __mutex_lock+0x119/0x1150\\n[52804.654423]        netlink_dump+0xb3/0x780\\n[52804.654845]        __netlink_dump_start+0x389/0x450\\n[52804.655321]        genl_family_rcv_msg_dumpit+0x155/0x1e0\\n[52804.655842]        genl_rcv_msg+0x1ed/0x3b0\\n[52804.656272]        netlink_rcv_skb+0xdc/0x210\\n[52804.656721]        genl_rcv+0x24/0x40\\n[52804.657119]        netlink_unicast+0x2f1/0x490\\n[52804.657570]        netlink_sendmsg+0x36d/0x660\\n[52804.658022]        __sock_sendmsg+0x73/0xc0\\n[52804.658450]        __sys_sendto+0x184/0x210\\n[52804.658877]        __x64_sys_sendto+0x72/0x80\\n[52804.659322]        do_syscall_64+0x6f/0x140\\n[52804.659752]        entry_SYSCALL_64_after_hwframe+0x46/0x4e\\n[52804.660281]\\n               other info that might help us debug this:\\n\\n[52804.661077]  Possible unsafe locking scenario:\\n\\n[52804.661671]        CPU0                    CPU1\\n[52804.662129]        ----                    ----\\n[52804.662577]   lock(dpll_lock);\\n[52804.662924]                                lock(nlk_cb_mutex-GENERIC);\\n[52804.663538]                                lock(dpll_lock);\\n[52804.664073]   lock(nlk_cb_mutex-GENERIC);\\n[52804.664490]\\n\\nThe issue as follows: __netlink_dump_start() calls control-\u003estart(cb)\\nwith nlk-\u003ecb_mutex held. In control-\u003estart(cb) the dpll_lock is taken.\\nThen nlk-\u003ecb_mutex is released and taken again in netlink_dump(), while\\ndpll_lock still being held. That leads to ABBA deadlock when another\\nCPU races with the same operation.\\n\\nFix this by moving dpll_lock taking into dumpit() callback which ensures\\ncorrect lock taking order.\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.7.6\", \"versionStartIncluding\": \"6.7\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.8\", \"versionStartIncluding\": \"6.7\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-05-11T20:02:56.186Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2024-26725\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-05-11T20:02:56.186Z\", \"dateReserved\": \"2024-02-19T14:20:24.163Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-04-03T14:55:24.074Z\", \"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.