{"api_version":"1","generated_at":"2026-11-20T07:30:05+00:00","cve":"CVE-2026-99738","urls":{"html":"https://cve.report/CVE-2026-99738","api":"https://cve.report/api/cve/CVE-2026-99738.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99738","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99738"},"summary":{"title":"mm/shmem: preserve allocation errors when swapping in large entries","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/shmem: preserve allocation errors when swapping in large entries\n\nshmem_swapin_folio() adjusts swap to the requested slot within a large\nswap entry before allocating a folio. If allocation or charging fails,\nthe error path compares this adjusted value with the original entry\nstill stored in the XArray in shmem_confirm_swap().\n\nUnless the index is at the start of the entry, this turns -ENOMEM into\n-EEXIST even though nothing changed.\n\nThe caller retries -EEXIST, so persistent allocation failures can leave\nthe task spinning instead of returning the error.\n\nRestore swap to index_entry on allocation failure so the existing error\npath checks the original entry. This preserves the allocation error if\nthe entry is unchanged and still retries if it changed concurrently.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-11-20 06:18:11","updated_at":"2026-11-20 06:18:11"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/f4ce23b1feef16d435aa1188b6c2a637a5373ed5","name":"https://git.kernel.org/stable/c/f4ce23b1feef16d435aa1188b6c2a637a5373ed5","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/680afc486db200e7b08307cb28be4f90766afcff","name":"https://git.kernel.org/stable/c/680afc486db200e7b08307cb28be4f90766afcff","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99738","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99738","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 91ab656ece137c368a3189dfd42f8c9203a6285c 680afc486db200e7b08307cb28be4f90766afcff git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 91ab656ece137c368a3189dfd42f8c9203a6285c f4ce23b1feef16d435aa1188b6c2a637a5373ed5 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.17","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.17 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3.5 7.3.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.4-rc2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["mm/shmem.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"680afc486db200e7b08307cb28be4f90766afcff","status":"affected","version":"91ab656ece137c368a3189dfd42f8c9203a6285c","versionType":"git"},{"lessThan":"f4ce23b1feef16d435aa1188b6c2a637a5373ed5","status":"affected","version":"91ab656ece137c368a3189dfd42f8c9203a6285c","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["mm/shmem.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.17"},{"lessThan":"6.17","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.3.*","status":"unaffected","version":"7.3.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.4-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3.5","versionStartIncluding":"6.17","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.4-rc2","versionStartIncluding":"6.17","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/shmem: preserve allocation errors when swapping in large entries\n\nshmem_swapin_folio() adjusts swap to the requested slot within a large\nswap entry before allocating a folio. If allocation or charging fails,\nthe error path compares this adjusted value with the original entry\nstill stored in the XArray in shmem_confirm_swap().\n\nUnless the index is at the start of the entry, this turns -ENOMEM into\n-EEXIST even though nothing changed.\n\nThe caller retries -EEXIST, so persistent allocation failures can leave\nthe task spinning instead of returning the error.\n\nRestore swap to index_entry on allocation failure so the existing error\npath checks the original entry. This preserves the allocation error if\nthe entry is unchanged and still retries if it changed concurrently."}],"providerMetadata":{"dateUpdated":"2026-11-20T05:51:11.250Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/680afc486db200e7b08307cb28be4f90766afcff"},{"url":"https://git.kernel.org/stable/c/f4ce23b1feef16d435aa1188b6c2a637a5373ed5"}],"title":"mm/shmem: preserve allocation errors when swapping in large entries","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99738","datePublished":"2026-11-20T05:51:11.250Z","dateReserved":"2026-09-25T10:25:14.431Z","dateUpdated":"2026-11-20T05:51:11.250Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-20 06:18:11","lastModifiedDate":"2026-11-20 06:18:11","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99738","Ordinal":"1","Title":"mm/shmem: preserve allocation errors when swapping in large entr","CVE":"CVE-2026-99738","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99738","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/shmem: preserve allocation errors when swapping in large entries\n\nshmem_swapin_folio() adjusts swap to the requested slot within a large\nswap entry before allocating a folio. If allocation or charging fails,\nthe error path compares this adjusted value with the original entry\nstill stored in the XArray in shmem_confirm_swap().\n\nUnless the index is at the start of the entry, this turns -ENOMEM into\n-EEXIST even though nothing changed.\n\nThe caller retries -EEXIST, so persistent allocation failures can leave\nthe task spinning instead of returning the error.\n\nRestore swap to index_entry on allocation failure so the existing error\npath checks the original entry. This preserves the allocation error if\nthe entry is unchanged and still retries if it changed concurrently.","Type":"Description","Title":"mm/shmem: preserve allocation errors when swapping in large entr"}]}}}