cve-2024-56751
Vulnerability from cvelistv5
Published
2024-12-29 11:30
Modified
2025-01-20 06:27
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: ipv6: release nexthop on device removal The CI is hitting some aperiodic hangup at device removal time in the pmtu.sh self-test: unregister_netdevice: waiting for veth_A-R1 to become free. Usage count = 6 ref_tracker: veth_A-R1@ffff888013df15d8 has 1/5 users at dst_init+0x84/0x4a0 dst_alloc+0x97/0x150 ip6_dst_alloc+0x23/0x90 ip6_rt_pcpu_alloc+0x1e6/0x520 ip6_pol_route+0x56f/0x840 fib6_rule_lookup+0x334/0x630 ip6_route_output_flags+0x259/0x480 ip6_dst_lookup_tail.constprop.0+0x5c2/0x940 ip6_dst_lookup_flow+0x88/0x190 udp_tunnel6_dst_lookup+0x2a7/0x4c0 vxlan_xmit_one+0xbde/0x4a50 [vxlan] vxlan_xmit+0x9ad/0xf20 [vxlan] dev_hard_start_xmit+0x10e/0x360 __dev_queue_xmit+0xf95/0x18c0 arp_solicit+0x4a2/0xe00 neigh_probe+0xaa/0xf0 While the first suspect is the dst_cache, explicitly tracking the dst owing the last device reference via probes proved such dst is held by the nexthop in the originating fib6_info. Similar to commit f5b51fe804ec ("ipv6: route: purge exception on removal"), we need to explicitly release the originating fib info when disconnecting a to-be-removed device from a live ipv6 dst: move the fib6_info cleanup into ip6_dst_ifdown(). Tested running: ./pmtu.sh cleanup_ipv6_exception in a tight loop for more than 400 iterations with no spat, running an unpatched kernel I observed a splat every ~10 iterations.
Impacted products
Vendor Product Version
Linux Linux Version: f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74
Version: f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74
Version: f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74
Version: f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74
Version: f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74
Create a notification for this product.
   Linux Linux Version: 5.3
Create a notification for this product.
Show details on NVD website


{
   containers: {
      cna: {
         affected: [
            {
               defaultStatus: "unaffected",
               product: "Linux",
               programFiles: [
                  "net/ipv6/route.c",
               ],
               repo: "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
               vendor: "Linux",
               versions: [
                  {
                     lessThan: "b2f26a27ea3f72f75d18330f76f5d1007c791848",
                     status: "affected",
                     version: "f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74",
                     versionType: "git",
                  },
                  {
                     lessThan: "43e25adc80269f917d2a195f0d59f74cdd182955",
                     status: "affected",
                     version: "f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74",
                     versionType: "git",
                  },
                  {
                     lessThan: "a3c3f8a4d025acc8c857246ec2b812c59102487a",
                     status: "affected",
                     version: "f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74",
                     versionType: "git",
                  },
                  {
                     lessThan: "0e4c6faaef8a24b762a24ffb767280e263ef8e10",
                     status: "affected",
                     version: "f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74",
                     versionType: "git",
                  },
                  {
                     lessThan: "eb02688c5c45c3e7af7e71f036a7144f5639cbfe",
                     status: "affected",
                     version: "f88d8ea67fbdbac7a64bfa6ed9a2ba27bb822f74",
                     versionType: "git",
                  },
               ],
            },
            {
               defaultStatus: "affected",
               product: "Linux",
               programFiles: [
                  "net/ipv6/route.c",
               ],
               repo: "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
               vendor: "Linux",
               versions: [
                  {
                     status: "affected",
                     version: "5.3",
                  },
                  {
                     lessThan: "5.3",
                     status: "unaffected",
                     version: "0",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "6.1.*",
                     status: "unaffected",
                     version: "6.1.120",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "6.6.*",
                     status: "unaffected",
                     version: "6.6.64",
                     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",
                  },
               ],
            },
         ],
         descriptions: [
            {
               lang: "en",
               value: "In the Linux kernel, the following vulnerability has been resolved:\n\nipv6: release nexthop on device removal\n\nThe CI is hitting some aperiodic hangup at device removal time in the\npmtu.sh self-test:\n\nunregister_netdevice: waiting for veth_A-R1 to become free. Usage count = 6\nref_tracker: veth_A-R1@ffff888013df15d8 has 1/5 users at\n\tdst_init+0x84/0x4a0\n\tdst_alloc+0x97/0x150\n\tip6_dst_alloc+0x23/0x90\n\tip6_rt_pcpu_alloc+0x1e6/0x520\n\tip6_pol_route+0x56f/0x840\n\tfib6_rule_lookup+0x334/0x630\n\tip6_route_output_flags+0x259/0x480\n\tip6_dst_lookup_tail.constprop.0+0x5c2/0x940\n\tip6_dst_lookup_flow+0x88/0x190\n\tudp_tunnel6_dst_lookup+0x2a7/0x4c0\n\tvxlan_xmit_one+0xbde/0x4a50 [vxlan]\n\tvxlan_xmit+0x9ad/0xf20 [vxlan]\n\tdev_hard_start_xmit+0x10e/0x360\n\t__dev_queue_xmit+0xf95/0x18c0\n\tarp_solicit+0x4a2/0xe00\n\tneigh_probe+0xaa/0xf0\n\nWhile the first suspect is the dst_cache, explicitly tracking the dst\nowing the last device reference via probes proved such dst is held by\nthe nexthop in the originating fib6_info.\n\nSimilar to commit f5b51fe804ec (\"ipv6: route: purge exception on\nremoval\"), we need to explicitly release the originating fib info when\ndisconnecting a to-be-removed device from a live ipv6 dst: move the\nfib6_info cleanup into ip6_dst_ifdown().\n\nTested running:\n\n./pmtu.sh cleanup_ipv6_exception\n\nin a tight loop for more than 400 iterations with no spat, running an\nunpatched kernel  I observed a splat every ~10 iterations.",
            },
         ],
         providerMetadata: {
            dateUpdated: "2025-01-20T06:27:23.379Z",
            orgId: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            shortName: "Linux",
         },
         references: [
            {
               url: "https://git.kernel.org/stable/c/b2f26a27ea3f72f75d18330f76f5d1007c791848",
            },
            {
               url: "https://git.kernel.org/stable/c/43e25adc80269f917d2a195f0d59f74cdd182955",
            },
            {
               url: "https://git.kernel.org/stable/c/a3c3f8a4d025acc8c857246ec2b812c59102487a",
            },
            {
               url: "https://git.kernel.org/stable/c/0e4c6faaef8a24b762a24ffb767280e263ef8e10",
            },
            {
               url: "https://git.kernel.org/stable/c/eb02688c5c45c3e7af7e71f036a7144f5639cbfe",
            },
         ],
         title: "ipv6: release nexthop on device removal",
         x_generator: {
            engine: "bippy-5f407fcff5a0",
         },
      },
   },
   cveMetadata: {
      assignerOrgId: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      assignerShortName: "Linux",
      cveId: "CVE-2024-56751",
      datePublished: "2024-12-29T11:30:16.805Z",
      dateReserved: "2024-12-29T11:26:39.759Z",
      dateUpdated: "2025-01-20T06:27:23.379Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
   "vulnerability-lookup:meta": {
      nvd: "{\"cve\":{\"id\":\"CVE-2024-56751\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-12-29T12:15:08.640\",\"lastModified\":\"2025-01-06T17:00:37.690\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nipv6: release nexthop on device removal\\n\\nThe CI is hitting some aperiodic hangup at device removal time in the\\npmtu.sh self-test:\\n\\nunregister_netdevice: waiting for veth_A-R1 to become free. Usage count = 6\\nref_tracker: veth_A-R1@ffff888013df15d8 has 1/5 users at\\n\\tdst_init+0x84/0x4a0\\n\\tdst_alloc+0x97/0x150\\n\\tip6_dst_alloc+0x23/0x90\\n\\tip6_rt_pcpu_alloc+0x1e6/0x520\\n\\tip6_pol_route+0x56f/0x840\\n\\tfib6_rule_lookup+0x334/0x630\\n\\tip6_route_output_flags+0x259/0x480\\n\\tip6_dst_lookup_tail.constprop.0+0x5c2/0x940\\n\\tip6_dst_lookup_flow+0x88/0x190\\n\\tudp_tunnel6_dst_lookup+0x2a7/0x4c0\\n\\tvxlan_xmit_one+0xbde/0x4a50 [vxlan]\\n\\tvxlan_xmit+0x9ad/0xf20 [vxlan]\\n\\tdev_hard_start_xmit+0x10e/0x360\\n\\t__dev_queue_xmit+0xf95/0x18c0\\n\\tarp_solicit+0x4a2/0xe00\\n\\tneigh_probe+0xaa/0xf0\\n\\nWhile the first suspect is the dst_cache, explicitly tracking the dst\\nowing the last device reference via probes proved such dst is held by\\nthe nexthop in the originating fib6_info.\\n\\nSimilar to commit f5b51fe804ec (\\\"ipv6: route: purge exception on\\nremoval\\\"), we need to explicitly release the originating fib info when\\ndisconnecting a to-be-removed device from a live ipv6 dst: move the\\nfib6_info cleanup into ip6_dst_ifdown().\\n\\nTested running:\\n\\n./pmtu.sh cleanup_ipv6_exception\\n\\nin a tight loop for more than 400 iterations with no spat, running an\\nunpatched kernel  I observed a splat every ~10 iterations.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ipv6: liberar el siguiente salto al eliminar el dispositivo. La CI está experimentando un bloqueo aperiódico en el momento de eliminar el dispositivo en la prueba automática pmtu.sh: unregister_netdevice: esperando a que veth_A-R1 se libere. Recuento de uso = 6 ref_tracker: veth_A-R1@ffff888013df15d8 tiene 1/5 usuarios en dst_init+0x84/0x4a0 dst_alloc+0x97/0x150 ip6_dst_alloc+0x23/0x90 ip6_rt_pcpu_alloc+0x1e6/0x520 ip6_pol_route+0x56f/0x840 fib6_rule_lookup+0x334/0x630 ip6_route_output_flags+0x259/0x480 ip6_dst_lookup_tail.constprop.0+0x5c2/0x940 ip6_dst_lookup_flow+0x88/0x190 udp_tunnel6_dst_lookup+0x2a7/0x4c0 vxlan_xmit_one+0xbde/0x4a50 [vxlan] vxlan_xmit+0x9ad/0xf20 [vxlan] dev_hard_start_xmit+0x10e/0x360 __dev_queue_xmit+0xf95/0x18c0 arp_solicit+0x4a2/0xe00 neigh_probe+0xaa/0xf0 Si bien el primer sospechoso es dst_cache, el seguimiento explícito del dst que debe la última referencia del dispositivo a través de sondas demostró que dicho dst se mantiene en el siguiente salto en el fib6_info de origen. Similar a el commit f5b51fe804ec (\\\"ipv6: route: purge exception on removal\\\"), necesitamos liberar explícitamente la información fib original al desconectar un dispositivo que se va a eliminar de un dst ipv6 activo: mueva la desinfección fib6_info a ip6_dst_ifdown(). Probado ejecutando: ./pmtu.sh cleanup_ipv6_exception en un bucle cerrado durante más de 400 iteraciones sin splat, ejecutando un kernel sin parchear Observé un splat cada ~10 iteraciones.\"}],\"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\":\"5.3\",\"versionEndExcluding\":\"6.1.120\",\"matchCriteriaId\":\"00376139-25FC-484F-BF0B-09AA1783B306\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.2\",\"versionEndExcluding\":\"6.6.64\",\"matchCriteriaId\":\"CA16DEE3-ABEC-4449-9F4A-7A3DC4FC36C7\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.7\",\"versionEndExcluding\":\"6.11.11\",\"matchCriteriaId\":\"21434379-192D-472F-9B54-D45E3650E893\"},{\"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/0e4c6faaef8a24b762a24ffb767280e263ef8e10\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/43e25adc80269f917d2a195f0d59f74cdd182955\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/a3c3f8a4d025acc8c857246ec2b812c59102487a\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/b2f26a27ea3f72f75d18330f76f5d1007c791848\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/eb02688c5c45c3e7af7e71f036a7144f5639cbfe\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}",
   },
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.