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

CVE-2024-53047 (GCVE-0-2024-53047)

Vulnerability from cvelistv5 – Published: 2024-11-19 17:19 – Updated: 2026-05-11 20:49
VLAI
Title
mptcp: init: protect sched with rcu_read_lock
Summary
In the Linux kernel, the following vulnerability has been resolved: mptcp: init: protect sched with rcu_read_lock Enabling CONFIG_PROVE_RCU_LIST with its dependence CONFIG_RCU_EXPERT creates this splat when an MPTCP socket is created: ============================= WARNING: suspicious RCU usage 6.12.0-rc2+ #11 Not tainted ----------------------------- net/mptcp/sched.c:44 RCU-list traversed in non-reader section!! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 no locks held by mptcp_connect/176. stack backtrace: CPU: 0 UID: 0 PID: 176 Comm: mptcp_connect Not tainted 6.12.0-rc2+ #11 Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:123) lockdep_rcu_suspicious (kernel/locking/lockdep.c:6822) mptcp_sched_find (net/mptcp/sched.c:44 (discriminator 7)) mptcp_init_sock (net/mptcp/protocol.c:2867 (discriminator 1)) ? sock_init_data_uid (arch/x86/include/asm/atomic.h:28) inet_create.part.0.constprop.0 (net/ipv4/af_inet.c:386) ? __sock_create (include/linux/rcupdate.h:347 (discriminator 1)) __sock_create (net/socket.c:1576) __sys_socket (net/socket.c:1671) ? __pfx___sys_socket (net/socket.c:1712) ? do_user_addr_fault (arch/x86/mm/fault.c:1419 (discriminator 1)) __x64_sys_socket (net/socket.c:1728) do_syscall_64 (arch/x86/entry/common.c:52 (discriminator 1)) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) That's because when the socket is initialised, rcu_read_lock() is not used despite the explicit comment written above the declaration of mptcp_sched_find() in sched.c. Adding the missing lock/unlock avoids the warning.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2025-10-01 20:13 UTC
CWE
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 1730b2b2c5a5a886007b247366aebe0976dc8881 , < cb8b81ad3e893a6d18dcdd3754cc2ea2a42c0136 (git)
Affected: 1730b2b2c5a5a886007b247366aebe0976dc8881 , < 494eb22f9a7bd03783e60595a57611c209175f1a (git)
Affected: 1730b2b2c5a5a886007b247366aebe0976dc8881 , < 3deb12c788c385e17142ce6ec50f769852fcec65 (git)
guessed Create a notification for this product.
Linux Linux Affected: 6.6
Unaffected: 0 , < 6.6 (semver)
Unaffected: 6.6.60 , ≤ 6.6.* (semver)
Unaffected: 6.11.7 , ≤ 6.11.* (semver)
Unaffected: 6.12 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "cvssV3_1": {
              "attackComplexity": "LOW",
              "attackVector": "LOCAL",
              "availabilityImpact": "HIGH",
              "baseScore": 5.5,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
              "version": "3.1"
            }
          },
          {
            "other": {
              "content": {
                "id": "CVE-2024-53047",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2025-10-01T20:13:27.074924Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "problemTypes": [
          {
            "descriptions": [
              {
                "cweId": "CWE-667",
                "description": "CWE-667 Improper Locking",
                "lang": "en",
                "type": "CWE"
              }
            ]
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2025-10-01T20:17:18.913Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/mptcp/protocol.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "cb8b81ad3e893a6d18dcdd3754cc2ea2a42c0136",
              "status": "affected",
              "version": "1730b2b2c5a5a886007b247366aebe0976dc8881",
              "versionType": "git"
            },
            {
              "lessThan": "494eb22f9a7bd03783e60595a57611c209175f1a",
              "status": "affected",
              "version": "1730b2b2c5a5a886007b247366aebe0976dc8881",
              "versionType": "git"
            },
            {
              "lessThan": "3deb12c788c385e17142ce6ec50f769852fcec65",
              "status": "affected",
              "version": "1730b2b2c5a5a886007b247366aebe0976dc8881",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "net/mptcp/protocol.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.6"
            },
            {
              "lessThan": "6.6",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.60",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.11.*",
              "status": "unaffected",
              "version": "6.11.7",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.12",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.60",
                  "versionStartIncluding": "6.6",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.11.7",
                  "versionStartIncluding": "6.6",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12",
                  "versionStartIncluding": "6.6",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: init: protect sched with rcu_read_lock\n\nEnabling CONFIG_PROVE_RCU_LIST with its dependence CONFIG_RCU_EXPERT\ncreates this splat when an MPTCP socket is created:\n\n  =============================\n  WARNING: suspicious RCU usage\n  6.12.0-rc2+ #11 Not tainted\n  -----------------------------\n  net/mptcp/sched.c:44 RCU-list traversed in non-reader section!!\n\n  other info that might help us debug this:\n\n  rcu_scheduler_active = 2, debug_locks = 1\n  no locks held by mptcp_connect/176.\n\n  stack backtrace:\n  CPU: 0 UID: 0 PID: 176 Comm: mptcp_connect Not tainted 6.12.0-rc2+ #11\n  Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011\n  Call Trace:\n   \u003cTASK\u003e\n   dump_stack_lvl (lib/dump_stack.c:123)\n   lockdep_rcu_suspicious (kernel/locking/lockdep.c:6822)\n   mptcp_sched_find (net/mptcp/sched.c:44 (discriminator 7))\n   mptcp_init_sock (net/mptcp/protocol.c:2867 (discriminator 1))\n   ? sock_init_data_uid (arch/x86/include/asm/atomic.h:28)\n   inet_create.part.0.constprop.0 (net/ipv4/af_inet.c:386)\n   ? __sock_create (include/linux/rcupdate.h:347 (discriminator 1))\n   __sock_create (net/socket.c:1576)\n   __sys_socket (net/socket.c:1671)\n   ? __pfx___sys_socket (net/socket.c:1712)\n   ? do_user_addr_fault (arch/x86/mm/fault.c:1419 (discriminator 1))\n   __x64_sys_socket (net/socket.c:1728)\n   do_syscall_64 (arch/x86/entry/common.c:52 (discriminator 1))\n   entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\n\nThat\u0027s because when the socket is initialised, rcu_read_lock() is not\nused despite the explicit comment written above the declaration of\nmptcp_sched_find() in sched.c. Adding the missing lock/unlock avoids the\nwarning."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-11T20:49:47.627Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/cb8b81ad3e893a6d18dcdd3754cc2ea2a42c0136"
        },
        {
          "url": "https://git.kernel.org/stable/c/494eb22f9a7bd03783e60595a57611c209175f1a"
        },
        {
          "url": "https://git.kernel.org/stable/c/3deb12c788c385e17142ce6ec50f769852fcec65"
        }
      ],
      "title": "mptcp: init: protect sched with rcu_read_lock",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-53047",
    "datePublished": "2024-11-19T17:19:34.036Z",
    "dateReserved": "2024-11-19T17:17:24.973Z",
    "dateUpdated": "2026-05-11T20:49:47.627Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2024-53047",
      "date": "2026-09-15",
      "epss": "0.00178",
      "percentile": "0.07548"
    },
    "fkie_nvd": {
      "configurations": "[{\"nodes\": [{\"operator\": \"OR\", \"negate\": false, \"cpeMatch\": [{\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"6.6\", \"versionEndExcluding\": \"6.6.60\", \"matchCriteriaId\": \"D65DC921-1258-459B-AC56-13B03E48CA9C\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"6.7\", \"versionEndExcluding\": \"6.11.7\", \"matchCriteriaId\": \"E96F53A4-5E87-4A70-BD9A-BC327828D57F\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*\", \"matchCriteriaId\": \"7F361E1D-580F-4A2D-A509-7615F73167A1\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:*\", \"matchCriteriaId\": \"925478D0-3E3D-4E6F-ACD5-09F28D5DF82C\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:6.12:rc3:*:*:*:*:*:*\", \"matchCriteriaId\": \"3C95E234-D335-4B6C-96BF-E2CEBD8654ED\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:6.12:rc4:*:*:*:*:*:*\", \"matchCriteriaId\": \"E0F717D8-3014-4F84-8086-0124B2111379\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:6.12:rc5:*:*:*:*:*:*\", \"matchCriteriaId\": \"24DBE6C7-2AAE-4818-AED2-E131F153D2FA\"}]}]}]",
      "descriptions": "[{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nmptcp: init: protect sched with rcu_read_lock\\n\\nEnabling CONFIG_PROVE_RCU_LIST with its dependence CONFIG_RCU_EXPERT\\ncreates this splat when an MPTCP socket is created:\\n\\n  =============================\\n  WARNING: suspicious RCU usage\\n  6.12.0-rc2+ #11 Not tainted\\n  -----------------------------\\n  net/mptcp/sched.c:44 RCU-list traversed in non-reader section!!\\n\\n  other info that might help us debug this:\\n\\n  rcu_scheduler_active = 2, debug_locks = 1\\n  no locks held by mptcp_connect/176.\\n\\n  stack backtrace:\\n  CPU: 0 UID: 0 PID: 176 Comm: mptcp_connect Not tainted 6.12.0-rc2+ #11\\n  Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011\\n  Call Trace:\\n   \u003cTASK\u003e\\n   dump_stack_lvl (lib/dump_stack.c:123)\\n   lockdep_rcu_suspicious (kernel/locking/lockdep.c:6822)\\n   mptcp_sched_find (net/mptcp/sched.c:44 (discriminator 7))\\n   mptcp_init_sock (net/mptcp/protocol.c:2867 (discriminator 1))\\n   ? sock_init_data_uid (arch/x86/include/asm/atomic.h:28)\\n   inet_create.part.0.constprop.0 (net/ipv4/af_inet.c:386)\\n   ? __sock_create (include/linux/rcupdate.h:347 (discriminator 1))\\n   __sock_create (net/socket.c:1576)\\n   __sys_socket (net/socket.c:1671)\\n   ? __pfx___sys_socket (net/socket.c:1712)\\n   ? do_user_addr_fault (arch/x86/mm/fault.c:1419 (discriminator 1))\\n   __x64_sys_socket (net/socket.c:1728)\\n   do_syscall_64 (arch/x86/entry/common.c:52 (discriminator 1))\\n   entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\\n\\nThat\u0027s because when the socket is initialised, rcu_read_lock() is not\\nused despite the explicit comment written above the declaration of\\nmptcp_sched_find() in sched.c. Adding the missing lock/unlock avoids the\\nwarning.\"}, {\"lang\": \"es\", \"value\": \"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: mptcp: init: proteger sched con rcu_read_lock Habilitar CONFIG_PROVE_RCU_LIST con su dependencia CONFIG_RCU_EXPERT crea este splat cuando se crea un socket MPTCP: ============================= ADVERTENCIA: uso sospechoso de RCU 6.12.0-rc2+ #11 No contaminado ----------------------------- net/mptcp/sched.c:44 \\u00a1Lista de RCU recorrida en una secci\\u00f3n que no es de lectura! Otra informaci\\u00f3n que podr\\u00eda ayudarnos a depurar esto: rcu_scheduler_active = 2, debug_locks = 1 no hay bloqueos retenidos por mptcp_connect/176. seguimiento de pila: CPU: 0 UID: 0 PID: 176 Comm: mptcp_connect No contaminado 6.12.0-rc2+ #11 Nombre del hardware: Bochs Bochs, BIOS Bochs 01/01/2011 Seguimiento de llamadas:  dump_stack_lvl (lib/dump_stack.c:123) lockdep_rcu_suspicious (kernel/locking/lockdep.c:6822) mptcp_sched_find (net/mptcp/sched.c:44 (discriminador 7)) mptcp_init_sock (net/mptcp/protocol.c:2867 (discriminador 1)) ? __sock_create (include/linux/rcupdate.h:347 (discriminador 1)) __sock_create (net/socket.c:1576) __sys_socket (net/socket.c:1671) ? __pfx___sys_socket (net/socket.c:1712) ? do_user_addr_fault (arch/x86/mm/fault.c:1419 (discriminator 1)) __x64_sys_socket (net/socket.c:1728) do_syscall_64 (arch/x86/entry/common.c:52 (discriminator 1)) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) Esto se debe a que cuando se inicializa el socket, no se utiliza rcu_read_lock() a pesar del comentario expl\\u00edcito escrito encima de la declaraci\\u00f3n de mptcp_sched_find() en sched.c. Agregar el bloqueo/desbloqueo faltante evita la advertencia.\"}]",
      "id": "CVE-2024-53047",
      "lastModified": "2024-11-27T20:28:03.473",
      "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-11-19T18:15:25.060",
      "references": "[{\"url\": \"https://git.kernel.org/stable/c/3deb12c788c385e17142ce6ec50f769852fcec65\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/494eb22f9a7bd03783e60595a57611c209175f1a\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/cb8b81ad3e893a6d18dcdd3754cc2ea2a42c0136\", \"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\": \"CWE-667\"}]}]"
    },
    "microsoft_vex": {
      "current_release_date": "2025-01-29T00:00:00.000Z",
      "cve": "CVE-2024-53047",
      "id": "msrc_CVE-2024-53047",
      "initial_release_date": "2024-11-02T00:00:00.000Z",
      "product_status:fixed": "2",
      "product_status:known_affected": "2",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "mptcp: init: protect sched with rcu_read_lock",
      "url": "https://msrc.microsoft.com/csaf/vex/2024/msrc_cve-2024-53047.json",
      "version": "1"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-53047\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-11-19T18:15:25.060\",\"lastModified\":\"2026-06-17T08:08:08.143\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nmptcp: init: protect sched with rcu_read_lock\\n\\nEnabling CONFIG_PROVE_RCU_LIST with its dependence CONFIG_RCU_EXPERT\\ncreates this splat when an MPTCP socket is created:\\n\\n  =============================\\n  WARNING: suspicious RCU usage\\n  6.12.0-rc2+ #11 Not tainted\\n  -----------------------------\\n  net/mptcp/sched.c:44 RCU-list traversed in non-reader section!!\\n\\n  other info that might help us debug this:\\n\\n  rcu_scheduler_active = 2, debug_locks = 1\\n  no locks held by mptcp_connect/176.\\n\\n  stack backtrace:\\n  CPU: 0 UID: 0 PID: 176 Comm: mptcp_connect Not tainted 6.12.0-rc2+ #11\\n  Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011\\n  Call Trace:\\n   \u003cTASK\u003e\\n   dump_stack_lvl (lib/dump_stack.c:123)\\n   lockdep_rcu_suspicious (kernel/locking/lockdep.c:6822)\\n   mptcp_sched_find (net/mptcp/sched.c:44 (discriminator 7))\\n   mptcp_init_sock (net/mptcp/protocol.c:2867 (discriminator 1))\\n   ? sock_init_data_uid (arch/x86/include/asm/atomic.h:28)\\n   inet_create.part.0.constprop.0 (net/ipv4/af_inet.c:386)\\n   ? __sock_create (include/linux/rcupdate.h:347 (discriminator 1))\\n   __sock_create (net/socket.c:1576)\\n   __sys_socket (net/socket.c:1671)\\n   ? __pfx___sys_socket (net/socket.c:1712)\\n   ? do_user_addr_fault (arch/x86/mm/fault.c:1419 (discriminator 1))\\n   __x64_sys_socket (net/socket.c:1728)\\n   do_syscall_64 (arch/x86/entry/common.c:52 (discriminator 1))\\n   entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\\n\\nThat\u0027s because when the socket is initialised, rcu_read_lock() is not\\nused despite the explicit comment written above the declaration of\\nmptcp_sched_find() in sched.c. Adding the missing lock/unlock avoids the\\nwarning.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: mptcp: init: proteger sched con rcu_read_lock Habilitar CONFIG_PROVE_RCU_LIST con su dependencia CONFIG_RCU_EXPERT crea este splat cuando se crea un socket MPTCP: ============================= ADVERTENCIA: uso sospechoso de RCU 6.12.0-rc2+ #11 No contaminado ----------------------------- net/mptcp/sched.c:44 \u00a1Lista de RCU recorrida en una secci\u00f3n que no es de lectura! Otra informaci\u00f3n que podr\u00eda ayudarnos a depurar esto: rcu_scheduler_active = 2, debug_locks = 1 no hay bloqueos retenidos por mptcp_connect/176. seguimiento de pila: CPU: 0 UID: 0 PID: 176 Comm: mptcp_connect No contaminado 6.12.0-rc2+ #11 Nombre del hardware: Bochs Bochs, BIOS Bochs 01/01/2011 Seguimiento de llamadas:  dump_stack_lvl (lib/dump_stack.c:123) lockdep_rcu_suspicious (kernel/locking/lockdep.c:6822) mptcp_sched_find (net/mptcp/sched.c:44 (discriminador 7)) mptcp_init_sock (net/mptcp/protocol.c:2867 (discriminador 1)) ? __sock_create (include/linux/rcupdate.h:347 (discriminador 1)) __sock_create (net/socket.c:1576) __sys_socket (net/socket.c:1671) ? __pfx___sys_socket (net/socket.c:1712) ? do_user_addr_fault (arch/x86/mm/fault.c:1419 (discriminator 1)) __x64_sys_socket (net/socket.c:1728) do_syscall_64 (arch/x86/entry/common.c:52 (discriminator 1)) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) Esto se debe a que cuando se inicializa el socket, no se utiliza rcu_read_lock() a pesar del comentario expl\u00edcito escrito encima de la declaraci\u00f3n de mptcp_sched_find() en sched.c. Agregar el bloqueo/desbloqueo faltante evita la advertencia.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"net/mptcp/protocol.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"1730b2b2c5a5a886007b247366aebe0976dc8881\",\"lessThan\":\"cb8b81ad3e893a6d18dcdd3754cc2ea2a42c0136\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"1730b2b2c5a5a886007b247366aebe0976dc8881\",\"lessThan\":\"494eb22f9a7bd03783e60595a57611c209175f1a\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"1730b2b2c5a5a886007b247366aebe0976dc8881\",\"lessThan\":\"3deb12c788c385e17142ce6ec50f769852fcec65\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"net/mptcp/protocol.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"6.6\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"6.6\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.6.60\",\"lessThanOrEqual\":\"6.6.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.11.7\",\"lessThanOrEqual\":\"6.11.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.12\",\"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},{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"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\":\"2025-10-01T20:13:27.074924Z\",\"id\":\"CVE-2024-53047\",\"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\"}]},{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"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.6\",\"versionEndExcluding\":\"6.6.60\",\"matchCriteriaId\":\"D65DC921-1258-459B-AC56-13B03E48CA9C\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.7\",\"versionEndExcluding\":\"6.11.7\",\"matchCriteriaId\":\"E96F53A4-5E87-4A70-BD9A-BC327828D57F\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"7F361E1D-580F-4A2D-A509-7615F73167A1\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:*\",\"matchCriteriaId\":\"925478D0-3E3D-4E6F-ACD5-09F28D5DF82C\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc3:*:*:*:*:*:*\",\"matchCriteriaId\":\"3C95E234-D335-4B6C-96BF-E2CEBD8654ED\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc4:*:*:*:*:*:*\",\"matchCriteriaId\":\"E0F717D8-3014-4F84-8086-0124B2111379\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc5:*:*:*:*:*:*\",\"matchCriteriaId\":\"24DBE6C7-2AAE-4818-AED2-E131F153D2FA\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/3deb12c788c385e17142ce6ec50f769852fcec65\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/494eb22f9a7bd03783e60595a57611c209175f1a\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/cb8b81ad3e893a6d18dcdd3754cc2ea2a42c0136\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}",
    "redhat_vex": {
      "aggregate_severity": "Low",
      "current_release_date": "2026-06-28T08:09:43+00:00",
      "cve": "CVE-2024-53047",
      "id": "CVE-2024-53047",
      "initial_release_date": "2024-11-19T00: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: mptcp: init: protect sched with rcu_read_lock",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-53047.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-09-12T16:56:52Z",
      "cve": "CVE-2024-53047",
      "id": "CVE-2024-53047",
      "initial_release_date": "2024-11-20T03:49:17Z",
      "product_status:known_not_affected": "477",
      "product_status:recommended": "43",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2024-53047",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2024-53047.json",
      "version": "25"
    },
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 5.5, \"attackVector\": \"LOCAL\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\", \"integrityImpact\": \"NONE\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"HIGH\", \"privilegesRequired\": \"LOW\", \"confidentialityImpact\": \"NONE\"}}, {\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-53047\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2025-10-01T20:13:27.074924Z\"}}}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-667\", \"description\": \"CWE-667 Improper Locking\"}]}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2025-10-01T15:28:54.432Z\"}}], \"cna\": {\"title\": \"mptcp: init: protect sched with rcu_read_lock\", \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"1730b2b2c5a5a886007b247366aebe0976dc8881\", \"lessThan\": \"cb8b81ad3e893a6d18dcdd3754cc2ea2a42c0136\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"1730b2b2c5a5a886007b247366aebe0976dc8881\", \"lessThan\": \"494eb22f9a7bd03783e60595a57611c209175f1a\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"1730b2b2c5a5a886007b247366aebe0976dc8881\", \"lessThan\": \"3deb12c788c385e17142ce6ec50f769852fcec65\", \"versionType\": \"git\"}], \"programFiles\": [\"net/mptcp/protocol.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.6\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"6.6\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"6.6.60\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.6.*\"}, {\"status\": \"unaffected\", \"version\": \"6.11.7\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.11.*\"}, {\"status\": \"unaffected\", \"version\": \"6.12\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"net/mptcp/protocol.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/cb8b81ad3e893a6d18dcdd3754cc2ea2a42c0136\"}, {\"url\": \"https://git.kernel.org/stable/c/494eb22f9a7bd03783e60595a57611c209175f1a\"}, {\"url\": \"https://git.kernel.org/stable/c/3deb12c788c385e17142ce6ec50f769852fcec65\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nmptcp: init: protect sched with rcu_read_lock\\n\\nEnabling CONFIG_PROVE_RCU_LIST with its dependence CONFIG_RCU_EXPERT\\ncreates this splat when an MPTCP socket is created:\\n\\n  =============================\\n  WARNING: suspicious RCU usage\\n  6.12.0-rc2+ #11 Not tainted\\n  -----------------------------\\n  net/mptcp/sched.c:44 RCU-list traversed in non-reader section!!\\n\\n  other info that might help us debug this:\\n\\n  rcu_scheduler_active = 2, debug_locks = 1\\n  no locks held by mptcp_connect/176.\\n\\n  stack backtrace:\\n  CPU: 0 UID: 0 PID: 176 Comm: mptcp_connect Not tainted 6.12.0-rc2+ #11\\n  Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011\\n  Call Trace:\\n   \u003cTASK\u003e\\n   dump_stack_lvl (lib/dump_stack.c:123)\\n   lockdep_rcu_suspicious (kernel/locking/lockdep.c:6822)\\n   mptcp_sched_find (net/mptcp/sched.c:44 (discriminator 7))\\n   mptcp_init_sock (net/mptcp/protocol.c:2867 (discriminator 1))\\n   ? sock_init_data_uid (arch/x86/include/asm/atomic.h:28)\\n   inet_create.part.0.constprop.0 (net/ipv4/af_inet.c:386)\\n   ? __sock_create (include/linux/rcupdate.h:347 (discriminator 1))\\n   __sock_create (net/socket.c:1576)\\n   __sys_socket (net/socket.c:1671)\\n   ? __pfx___sys_socket (net/socket.c:1712)\\n   ? do_user_addr_fault (arch/x86/mm/fault.c:1419 (discriminator 1))\\n   __x64_sys_socket (net/socket.c:1728)\\n   do_syscall_64 (arch/x86/entry/common.c:52 (discriminator 1))\\n   entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\\n\\nThat\u0027s because when the socket is initialised, rcu_read_lock() is not\\nused despite the explicit comment written above the declaration of\\nmptcp_sched_find() in sched.c. Adding the missing lock/unlock avoids the\\nwarning.\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.6.60\", \"versionStartIncluding\": \"6.6\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.11.7\", \"versionStartIncluding\": \"6.6\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.12\", \"versionStartIncluding\": \"6.6\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-05-11T20:49:47.627Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2024-53047\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-05-11T20:49:47.627Z\", \"dateReserved\": \"2024-11-19T17:17:24.973Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-11-19T17:19:34.036Z\", \"assignerShortName\": \"Linux\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

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.


Loading…