CVE-2024-53212 (GCVE-0-2024-53212)

Vulnerability from cvelistv5 – Published: 2024-12-27 13:49 – Updated: 2025-05-04 09:56
VLAI?
Summary
In the Linux kernel, the following vulnerability has been resolved: netlink: fix false positive warning in extack during dumps Commit under fixes extended extack reporting to dumps. It works under normal conditions, because extack errors are usually reported during ->start() or the first ->dump(), it's quite rare that the dump starts okay but fails later. If the dump does fail later, however, the input skb will already have the initiating message pulled, so checking if bad attr falls within skb->data will fail. Switch the check to using nlh, which is always valid. syzbot found a way to hit that scenario by filling up the receive queue. In this case we initiate a dump but don't call ->dump() until there is read space for an skb. WARNING: CPU: 1 PID: 5845 at net/netlink/af_netlink.c:2210 netlink_ack_tlv_fill+0x1a8/0x560 net/netlink/af_netlink.c:2209 RIP: 0010:netlink_ack_tlv_fill+0x1a8/0x560 net/netlink/af_netlink.c:2209 Call Trace: <TASK> netlink_dump_done+0x513/0x970 net/netlink/af_netlink.c:2250 netlink_dump+0x91f/0xe10 net/netlink/af_netlink.c:2351 netlink_recvmsg+0x6bb/0x11d0 net/netlink/af_netlink.c:1983 sock_recvmsg_nosec net/socket.c:1051 [inline] sock_recvmsg+0x22f/0x280 net/socket.c:1073 __sys_recvfrom+0x246/0x3d0 net/socket.c:2267 __do_sys_recvfrom net/socket.c:2285 [inline] __se_sys_recvfrom net/socket.c:2281 [inline] __x64_sys_recvfrom+0xde/0x100 net/socket.c:2281 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7ff37dd17a79
Severity ?
No CVSS data available.
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: 8af4f60472fce1f22db5068107b37bcc1a65eabd , < 6406d0ce0414b807af5d2a4b781c3f3ee52b8a4d (git)
Affected: 8af4f60472fce1f22db5068107b37bcc1a65eabd , < 28af028a71371df5fcbf807fd4444bba8d0c33cc (git)
Affected: 8af4f60472fce1f22db5068107b37bcc1a65eabd , < 3bf39fa849ab8ed52abb6715922e6102d3df9f97 (git)
Create a notification for this product.
    Linux Linux Affected: 6.10
Unaffected: 0 , < 6.10 (semver)
Unaffected: 6.11.11 , ≤ 6.11.* (semver)
Unaffected: 6.12.2 , ≤ 6.12.* (semver)
Unaffected: 6.13 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/netlink/af_netlink.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "6406d0ce0414b807af5d2a4b781c3f3ee52b8a4d",
              "status": "affected",
              "version": "8af4f60472fce1f22db5068107b37bcc1a65eabd",
              "versionType": "git"
            },
            {
              "lessThan": "28af028a71371df5fcbf807fd4444bba8d0c33cc",
              "status": "affected",
              "version": "8af4f60472fce1f22db5068107b37bcc1a65eabd",
              "versionType": "git"
            },
            {
              "lessThan": "3bf39fa849ab8ed52abb6715922e6102d3df9f97",
              "status": "affected",
              "version": "8af4f60472fce1f22db5068107b37bcc1a65eabd",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "net/netlink/af_netlink.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.10"
            },
            {
              "lessThan": "6.10",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.11.*",
              "status": "unaffected",
              "version": "6.11.11",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.2",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.13",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.11.11",
                  "versionStartIncluding": "6.10",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.2",
                  "versionStartIncluding": "6.10",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.13",
                  "versionStartIncluding": "6.10",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnetlink: fix false positive warning in extack during dumps\n\nCommit under fixes extended extack reporting to dumps.\nIt works under normal conditions, because extack errors are\nusually reported during -\u003estart() or the first -\u003edump(),\nit\u0027s quite rare that the dump starts okay but fails later.\nIf the dump does fail later, however, the input skb will\nalready have the initiating message pulled, so checking\nif bad attr falls within skb-\u003edata will fail.\n\nSwitch the check to using nlh, which is always valid.\n\nsyzbot found a way to hit that scenario by filling up\nthe receive queue. In this case we initiate a dump\nbut don\u0027t call -\u003edump() until there is read space for\nan skb.\n\nWARNING: CPU: 1 PID: 5845 at net/netlink/af_netlink.c:2210 netlink_ack_tlv_fill+0x1a8/0x560 net/netlink/af_netlink.c:2209\nRIP: 0010:netlink_ack_tlv_fill+0x1a8/0x560 net/netlink/af_netlink.c:2209\nCall Trace:\n \u003cTASK\u003e\n netlink_dump_done+0x513/0x970 net/netlink/af_netlink.c:2250\n netlink_dump+0x91f/0xe10 net/netlink/af_netlink.c:2351\n netlink_recvmsg+0x6bb/0x11d0 net/netlink/af_netlink.c:1983\n sock_recvmsg_nosec net/socket.c:1051 [inline]\n sock_recvmsg+0x22f/0x280 net/socket.c:1073\n __sys_recvfrom+0x246/0x3d0 net/socket.c:2267\n __do_sys_recvfrom net/socket.c:2285 [inline]\n __se_sys_recvfrom net/socket.c:2281 [inline]\n __x64_sys_recvfrom+0xde/0x100 net/socket.c:2281\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n RIP: 0033:0x7ff37dd17a79"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-05-04T09:56:02.916Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/6406d0ce0414b807af5d2a4b781c3f3ee52b8a4d"
        },
        {
          "url": "https://git.kernel.org/stable/c/28af028a71371df5fcbf807fd4444bba8d0c33cc"
        },
        {
          "url": "https://git.kernel.org/stable/c/3bf39fa849ab8ed52abb6715922e6102d3df9f97"
        }
      ],
      "title": "netlink: fix false positive warning in extack during dumps",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-53212",
    "datePublished": "2024-12-27T13:49:57.904Z",
    "dateReserved": "2024-11-19T17:17:25.021Z",
    "dateUpdated": "2025-05-04T09:56:02.916Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "fkie_nvd": {
      "descriptions": "[{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnetlink: fix false positive warning in extack during dumps\\n\\nCommit under fixes extended extack reporting to dumps.\\nIt works under normal conditions, because extack errors are\\nusually reported during -\u003estart() or the first -\u003edump(),\\nit\u0027s quite rare that the dump starts okay but fails later.\\nIf the dump does fail later, however, the input skb will\\nalready have the initiating message pulled, so checking\\nif bad attr falls within skb-\u003edata will fail.\\n\\nSwitch the check to using nlh, which is always valid.\\n\\nsyzbot found a way to hit that scenario by filling up\\nthe receive queue. In this case we initiate a dump\\nbut don\u0027t call -\u003edump() until there is read space for\\nan skb.\\n\\nWARNING: CPU: 1 PID: 5845 at net/netlink/af_netlink.c:2210 netlink_ack_tlv_fill+0x1a8/0x560 net/netlink/af_netlink.c:2209\\nRIP: 0010:netlink_ack_tlv_fill+0x1a8/0x560 net/netlink/af_netlink.c:2209\\nCall Trace:\\n \u003cTASK\u003e\\n netlink_dump_done+0x513/0x970 net/netlink/af_netlink.c:2250\\n netlink_dump+0x91f/0xe10 net/netlink/af_netlink.c:2351\\n netlink_recvmsg+0x6bb/0x11d0 net/netlink/af_netlink.c:1983\\n sock_recvmsg_nosec net/socket.c:1051 [inline]\\n sock_recvmsg+0x22f/0x280 net/socket.c:1073\\n __sys_recvfrom+0x246/0x3d0 net/socket.c:2267\\n __do_sys_recvfrom net/socket.c:2285 [inline]\\n __se_sys_recvfrom net/socket.c:2281 [inline]\\n __x64_sys_recvfrom+0xde/0x100 net/socket.c:2281\\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\\n do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83\\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\\n RIP: 0033:0x7ff37dd17a79\"}, {\"lang\": \"es\", \"value\": \"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: netlink: corrige la advertencia de falso positivo en extack durante los volcados Commit bajo corrige el informe extendido de extack a los volcados. Funciona en condiciones normales, porque los errores de extack generalmente se informan durante -\u0026gt;start() o el primer -\u0026gt;dump(), es bastante raro que el volcado comience bien pero falle m\\u00e1s tarde. Sin embargo, si el volcado falla m\\u00e1s tarde, el skb de entrada ya tendr\\u00e1 el mensaje de inicio extra\\u00eddo, por lo que la verificaci\\u00f3n de si el atributo incorrecto cae dentro de skb-\u0026gt;data fallar\\u00e1. Cambie la verificaci\\u00f3n para usar nlh, que siempre es v\\u00e1lido. syzbot encontr\\u00f3 una forma de abordar ese escenario llenando la cola de recepci\\u00f3n. En este caso, iniciamos un volcado pero no llamamos a -\u0026gt;dump() hasta que haya espacio de lectura para un skb. ADVERTENCIA: CPU: 1 PID: 5845 en net/netlink/af_netlink.c:2210 netlink_ack_tlv_fill+0x1a8/0x560 net/netlink/af_netlink.c:2209 RIP: 0010:netlink_ack_tlv_fill+0x1a8/0x560 net/netlink/af_netlink.c:2209 Seguimiento de llamadas:  netlink_dump_done+0x513/0x970 net/netlink/af_netlink.c:2250 netlink_dump+0x91f/0xe10 net/netlink/af_netlink.c:2351 netlink_recvmsg+0x6bb/0x11d0 net/netlink/af_netlink.c:1983 sock_recvmsg_nosec net/socket.c:1051 [en l\\u00ednea] sock_recvmsg+0x22f/0x280 net/socket.c:1073 __sys_recvfrom+0x246/0x3d0 net/socket.c:2267 __do_sys_recvfrom net/socket.c:2285 [en l\\u00ednea] __se_sys_recvfrom net/socket.c:2281 [en l\\u00ednea] __x64_sys_recvfrom+0xde/0x100 net/socket.c:2281 do_syscall_x64 arch/x86/entry/common.c:52 [en l\\u00ednea] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entrada_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7ff37dd17a79\"}]",
      "id": "CVE-2024-53212",
      "lastModified": "2024-12-27T14:15:29.130",
      "published": "2024-12-27T14:15:29.130",
      "references": "[{\"url\": \"https://git.kernel.org/stable/c/28af028a71371df5fcbf807fd4444bba8d0c33cc\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/3bf39fa849ab8ed52abb6715922e6102d3df9f97\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/6406d0ce0414b807af5d2a4b781c3f3ee52b8a4d\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]",
      "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "vulnStatus": "Awaiting Analysis"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-53212\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-12-27T14:15:29.130\",\"lastModified\":\"2025-10-08T14:04:53.860\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnetlink: fix false positive warning in extack during dumps\\n\\nCommit under fixes extended extack reporting to dumps.\\nIt works under normal conditions, because extack errors are\\nusually reported during -\u003estart() or the first -\u003edump(),\\nit\u0027s quite rare that the dump starts okay but fails later.\\nIf the dump does fail later, however, the input skb will\\nalready have the initiating message pulled, so checking\\nif bad attr falls within skb-\u003edata will fail.\\n\\nSwitch the check to using nlh, which is always valid.\\n\\nsyzbot found a way to hit that scenario by filling up\\nthe receive queue. In this case we initiate a dump\\nbut don\u0027t call -\u003edump() until there is read space for\\nan skb.\\n\\nWARNING: CPU: 1 PID: 5845 at net/netlink/af_netlink.c:2210 netlink_ack_tlv_fill+0x1a8/0x560 net/netlink/af_netlink.c:2209\\nRIP: 0010:netlink_ack_tlv_fill+0x1a8/0x560 net/netlink/af_netlink.c:2209\\nCall Trace:\\n \u003cTASK\u003e\\n netlink_dump_done+0x513/0x970 net/netlink/af_netlink.c:2250\\n netlink_dump+0x91f/0xe10 net/netlink/af_netlink.c:2351\\n netlink_recvmsg+0x6bb/0x11d0 net/netlink/af_netlink.c:1983\\n sock_recvmsg_nosec net/socket.c:1051 [inline]\\n sock_recvmsg+0x22f/0x280 net/socket.c:1073\\n __sys_recvfrom+0x246/0x3d0 net/socket.c:2267\\n __do_sys_recvfrom net/socket.c:2285 [inline]\\n __se_sys_recvfrom net/socket.c:2281 [inline]\\n __x64_sys_recvfrom+0xde/0x100 net/socket.c:2281\\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\\n do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83\\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\\n RIP: 0033:0x7ff37dd17a79\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: netlink: corrige la advertencia de falso positivo en extack durante los volcados Commit bajo corrige el informe extendido de extack a los volcados. Funciona en condiciones normales, porque los errores de extack generalmente se informan durante -\u0026gt;start() o el primer -\u0026gt;dump(), es bastante raro que el volcado comience bien pero falle m\u00e1s tarde. Sin embargo, si el volcado falla m\u00e1s tarde, el skb de entrada ya tendr\u00e1 el mensaje de inicio extra\u00eddo, por lo que la verificaci\u00f3n de si el atributo incorrecto cae dentro de skb-\u0026gt;data fallar\u00e1. Cambie la verificaci\u00f3n para usar nlh, que siempre es v\u00e1lido. syzbot encontr\u00f3 una forma de abordar ese escenario llenando la cola de recepci\u00f3n. En este caso, iniciamos un volcado pero no llamamos a -\u0026gt;dump() hasta que haya espacio de lectura para un skb. ADVERTENCIA: CPU: 1 PID: 5845 en net/netlink/af_netlink.c:2210 netlink_ack_tlv_fill+0x1a8/0x560 net/netlink/af_netlink.c:2209 RIP: 0010:netlink_ack_tlv_fill+0x1a8/0x560 net/netlink/af_netlink.c:2209 Seguimiento de llamadas:  netlink_dump_done+0x513/0x970 net/netlink/af_netlink.c:2250 netlink_dump+0x91f/0xe10 net/netlink/af_netlink.c:2351 netlink_recvmsg+0x6bb/0x11d0 net/netlink/af_netlink.c:1983 sock_recvmsg_nosec net/socket.c:1051 [en l\u00ednea] sock_recvmsg+0x22f/0x280 net/socket.c:1073 __sys_recvfrom+0x246/0x3d0 net/socket.c:2267 __do_sys_recvfrom net/socket.c:2285 [en l\u00ednea] __se_sys_recvfrom net/socket.c:2281 [en l\u00ednea] __x64_sys_recvfrom+0xde/0x100 net/socket.c:2281 do_syscall_x64 arch/x86/entry/common.c:52 [en l\u00ednea] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entrada_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7ff37dd17a79\"}],\"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}]},\"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.10\",\"versionEndExcluding\":\"6.11.11\",\"matchCriteriaId\":\"158A6B22-9260-41D7-965A-A81798A5A969\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.12\",\"versionEndExcluding\":\"6.12.2\",\"matchCriteriaId\":\"D8882B1B-2ABC-4838-AC1D-DBDBB5764776\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/28af028a71371df5fcbf807fd4444bba8d0c33cc\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/3bf39fa849ab8ed52abb6715922e6102d3df9f97\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/6406d0ce0414b807af5d2a4b781c3f3ee52b8a4d\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

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.