{"api_version":"1","generated_at":"2026-09-11T09:01:57+00:00","cve":"CVE-2026-80784","urls":{"html":"https://cve.report/CVE-2026-80784","api":"https://cve.report/api/cve/CVE-2026-80784.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-80784","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-80784"},"summary":{"title":"mptcp: pm: fix memory leak from alloc-during-teardown race","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: pm: fix memory leak from alloc-during-teardown race\n\nmptcp_pm_destroy() empties msk->pm.anno_list and\nmsk->pm.userspace_pm_local_addr_list under msk->pm.lock during socket\nteardown, dropping the lock between the two.\n\nA concurrent userspace PM genl ANNOUNCE on the same msk holds a sock\nreference via mptcp_token_get_sock() and, in\nmptcp_pm_nl_announce_doit(), calls\nmptcp_userspace_pm_append_new_local_addr() and\nmptcp_pm_announced_alloc(). Both take msk->pm.lock briefly to add to\ntheir respective lists. Because the genl handler holds a sock reference,\nmptcp_pm_destroy() may run on the same msk via mptcp_disconnect(), which\ninvokes mptcp_destroy_common() without dropping the sock refcount,\nbefore the handler completes.\n\nIf the lock acquisitions interleave such that mptcp_pm_destroy() empties\na list first, the later alloc adds its entry to a list head that nothing\nelse iterates for this msk, and the entry leaks. kmemleak reports both\nmptcp_pm_add_addr objects (from mptcp_pm_announced_alloc()) and\nmptcp_pm_addr_entry objects (from\nmptcp_userspace_pm_append_new_local_addr()) under sustained concurrent\nANNOUNCE + close load against the userspace PM.\n\nAdd an MPTCP_PM_DESTROYING bit in msk->pm.status, set by\nmptcp_pm_destroy() under pm.lock before the lists are emptied and\nchecked under pm.lock by the alloc paths. Either the alloc takes pm.lock\nfirst, in which case its entry is on the list when mptcp_pm_destroy()\nfrees it; or mptcp_pm_destroy() takes pm.lock first, in which case the\nlater alloc observes the bit and refuses.\n\nFound by an MPTCP protocol-flow harness extending BRF (arXiv:2305.08782).","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-04 16:18:04","updated_at":"2026-09-04 16:18:04"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/6c290915a03fc8228b473641025cf762b256dbd2","name":"https://git.kernel.org/stable/c/6c290915a03fc8228b473641025cf762b256dbd2","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/bb32e9a6a9a9f99eeda16c4efe443400f3e43892","name":"https://git.kernel.org/stable/c/bb32e9a6a9a9f99eeda16c4efe443400f3e43892","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/b2a0b55bf613bd3e81ed26a847b0f6b8e6b7f804","name":"https://git.kernel.org/stable/c/b2a0b55bf613bd3e81ed26a847b0f6b8e6b7f804","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/9fe5eebb664ecdba88f3fde18062d94b1d1c465f","name":"https://git.kernel.org/stable/c/9fe5eebb664ecdba88f3fde18062d94b1d1c465f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/f48341830e4202db3fe884b819b2db6740f0537d","name":"https://git.kernel.org/stable/c/f48341830e4202db3fe884b819b2db6740f0537d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/efc33b5102ff859bacd390a5f30112d8e0c084c0","name":"https://git.kernel.org/stable/c/efc33b5102ff859bacd390a5f30112d8e0c084c0","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-80784","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80784","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9ab4807c84a4aacfc9b4f79cc81254035e0ec361 f48341830e4202db3fe884b819b2db6740f0537d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9ab4807c84a4aacfc9b4f79cc81254035e0ec361 bb32e9a6a9a9f99eeda16c4efe443400f3e43892 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9ab4807c84a4aacfc9b4f79cc81254035e0ec361 b2a0b55bf613bd3e81ed26a847b0f6b8e6b7f804 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9ab4807c84a4aacfc9b4f79cc81254035e0ec361 9fe5eebb664ecdba88f3fde18062d94b1d1c465f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9ab4807c84a4aacfc9b4f79cc81254035e0ec361 6c290915a03fc8228b473641025cf762b256dbd2 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9ab4807c84a4aacfc9b4f79cc81254035e0ec361 efc33b5102ff859bacd390a5f30112d8e0c084c0 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.19","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.19 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.1.187 6.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6.154 6.6.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.106 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.47 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.11 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"80784","cve":"CVE-2026-80784","epss":"0.001730000","percentile":"0.068310000","score_date":"2026-09-07","updated_at":"2026-09-08 00:05:27"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["net/mptcp/pm.c","net/mptcp/pm_userspace.c","net/mptcp/protocol.h"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"f48341830e4202db3fe884b819b2db6740f0537d","status":"affected","version":"9ab4807c84a4aacfc9b4f79cc81254035e0ec361","versionType":"git"},{"lessThan":"bb32e9a6a9a9f99eeda16c4efe443400f3e43892","status":"affected","version":"9ab4807c84a4aacfc9b4f79cc81254035e0ec361","versionType":"git"},{"lessThan":"b2a0b55bf613bd3e81ed26a847b0f6b8e6b7f804","status":"affected","version":"9ab4807c84a4aacfc9b4f79cc81254035e0ec361","versionType":"git"},{"lessThan":"9fe5eebb664ecdba88f3fde18062d94b1d1c465f","status":"affected","version":"9ab4807c84a4aacfc9b4f79cc81254035e0ec361","versionType":"git"},{"lessThan":"6c290915a03fc8228b473641025cf762b256dbd2","status":"affected","version":"9ab4807c84a4aacfc9b4f79cc81254035e0ec361","versionType":"git"},{"lessThan":"efc33b5102ff859bacd390a5f30112d8e0c084c0","status":"affected","version":"9ab4807c84a4aacfc9b4f79cc81254035e0ec361","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["net/mptcp/pm.c","net/mptcp/pm_userspace.c","net/mptcp/protocol.h"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.19"},{"lessThan":"5.19","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.1.*","status":"unaffected","version":"6.1.187","versionType":"semver"},{"lessThanOrEqual":"6.6.*","status":"unaffected","version":"6.6.154","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.106","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.47","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.11","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.1.187","versionStartIncluding":"5.19","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.6.154","versionStartIncluding":"5.19","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.106","versionStartIncluding":"5.19","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.47","versionStartIncluding":"5.19","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.11","versionStartIncluding":"5.19","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","versionStartIncluding":"5.19","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: pm: fix memory leak from alloc-during-teardown race\n\nmptcp_pm_destroy() empties msk->pm.anno_list and\nmsk->pm.userspace_pm_local_addr_list under msk->pm.lock during socket\nteardown, dropping the lock between the two.\n\nA concurrent userspace PM genl ANNOUNCE on the same msk holds a sock\nreference via mptcp_token_get_sock() and, in\nmptcp_pm_nl_announce_doit(), calls\nmptcp_userspace_pm_append_new_local_addr() and\nmptcp_pm_announced_alloc(). Both take msk->pm.lock briefly to add to\ntheir respective lists. Because the genl handler holds a sock reference,\nmptcp_pm_destroy() may run on the same msk via mptcp_disconnect(), which\ninvokes mptcp_destroy_common() without dropping the sock refcount,\nbefore the handler completes.\n\nIf the lock acquisitions interleave such that mptcp_pm_destroy() empties\na list first, the later alloc adds its entry to a list head that nothing\nelse iterates for this msk, and the entry leaks. kmemleak reports both\nmptcp_pm_add_addr objects (from mptcp_pm_announced_alloc()) and\nmptcp_pm_addr_entry objects (from\nmptcp_userspace_pm_append_new_local_addr()) under sustained concurrent\nANNOUNCE + close load against the userspace PM.\n\nAdd an MPTCP_PM_DESTROYING bit in msk->pm.status, set by\nmptcp_pm_destroy() under pm.lock before the lists are emptied and\nchecked under pm.lock by the alloc paths. Either the alloc takes pm.lock\nfirst, in which case its entry is on the list when mptcp_pm_destroy()\nfrees it; or mptcp_pm_destroy() takes pm.lock first, in which case the\nlater alloc observes the bit and refuses.\n\nFound by an MPTCP protocol-flow harness extending BRF (arXiv:2305.08782)."}],"providerMetadata":{"dateUpdated":"2026-09-04T15:12:56.125Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/f48341830e4202db3fe884b819b2db6740f0537d"},{"url":"https://git.kernel.org/stable/c/bb32e9a6a9a9f99eeda16c4efe443400f3e43892"},{"url":"https://git.kernel.org/stable/c/b2a0b55bf613bd3e81ed26a847b0f6b8e6b7f804"},{"url":"https://git.kernel.org/stable/c/9fe5eebb664ecdba88f3fde18062d94b1d1c465f"},{"url":"https://git.kernel.org/stable/c/6c290915a03fc8228b473641025cf762b256dbd2"},{"url":"https://git.kernel.org/stable/c/efc33b5102ff859bacd390a5f30112d8e0c084c0"}],"title":"mptcp: pm: fix memory leak from alloc-during-teardown race","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-80784","datePublished":"2026-09-04T15:12:56.125Z","dateReserved":"2026-08-26T14:34:25.792Z","dateUpdated":"2026-09-04T15:12:56.125Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-04 16:18:04","lastModifiedDate":"2026-09-04 16:18:04","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"80784","Ordinal":"1","Title":"mptcp: pm: fix memory leak from alloc-during-teardown race","CVE":"CVE-2026-80784","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"80784","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: pm: fix memory leak from alloc-during-teardown race\n\nmptcp_pm_destroy() empties msk->pm.anno_list and\nmsk->pm.userspace_pm_local_addr_list under msk->pm.lock during socket\nteardown, dropping the lock between the two.\n\nA concurrent userspace PM genl ANNOUNCE on the same msk holds a sock\nreference via mptcp_token_get_sock() and, in\nmptcp_pm_nl_announce_doit(), calls\nmptcp_userspace_pm_append_new_local_addr() and\nmptcp_pm_announced_alloc(). Both take msk->pm.lock briefly to add to\ntheir respective lists. Because the genl handler holds a sock reference,\nmptcp_pm_destroy() may run on the same msk via mptcp_disconnect(), which\ninvokes mptcp_destroy_common() without dropping the sock refcount,\nbefore the handler completes.\n\nIf the lock acquisitions interleave such that mptcp_pm_destroy() empties\na list first, the later alloc adds its entry to a list head that nothing\nelse iterates for this msk, and the entry leaks. kmemleak reports both\nmptcp_pm_add_addr objects (from mptcp_pm_announced_alloc()) and\nmptcp_pm_addr_entry objects (from\nmptcp_userspace_pm_append_new_local_addr()) under sustained concurrent\nANNOUNCE + close load against the userspace PM.\n\nAdd an MPTCP_PM_DESTROYING bit in msk->pm.status, set by\nmptcp_pm_destroy() under pm.lock before the lists are emptied and\nchecked under pm.lock by the alloc paths. Either the alloc takes pm.lock\nfirst, in which case its entry is on the list when mptcp_pm_destroy()\nfrees it; or mptcp_pm_destroy() takes pm.lock first, in which case the\nlater alloc observes the bit and refuses.\n\nFound by an MPTCP protocol-flow harness extending BRF (arXiv:2305.08782).","Type":"Description","Title":"mptcp: pm: fix memory leak from alloc-during-teardown race"}]}}}