CVE-2024-53047
Vulnerability from cvelistv5
Published
2024-11-19 17:19
Modified
2024-11-19 17:19
Severity ?
Summary
mptcp: init: protect sched with rcu_read_lock
Impacted products
LinuxLinux
LinuxLinux
Show details on NVD website


{
  "containers": {
    "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": "cb8b81ad3e89",
              "status": "affected",
              "version": "1730b2b2c5a5",
              "versionType": "git"
            },
            {
              "lessThan": "494eb22f9a7b",
              "status": "affected",
              "version": "1730b2b2c5a5",
              "versionType": "git"
            },
            {
              "lessThan": "3deb12c788c3",
              "status": "affected",
              "version": "1730b2b2c5a5",
              "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"
            }
          ]
        }
      ],
      "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": "2024-11-19T17:19:34.036Z",
        "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-8e903de6a542"
      }
    }
  },
  "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": "2024-11-19T17:19:34.036Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-53047\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-11-19T18:15:25.060\",\"lastModified\":\"2024-11-19T21:56:45.533\",\"vulnStatus\":\"Awaiting Analysis\",\"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.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/3deb12c788c385e17142ce6ec50f769852fcec65\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/494eb22f9a7bd03783e60595a57611c209175f1a\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/cb8b81ad3e893a6d18dcdd3754cc2ea2a42c0136\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




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.