{"api_version":"1","generated_at":"2026-11-20T07:30:00+00:00","cve":"CVE-2026-99749","urls":{"html":"https://cve.report/CVE-2026-99749","api":"https://cve.report/api/cve/CVE-2026-99749.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99749","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99749"},"summary":{"title":"ksmbd: enforce the read-only share flag when creating a stream","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: enforce the read-only share flag when creating a stream\n\nWhen a share is read-only, smb2_open() rejects opens that would create\nor truncate a file. Creating a named stream on an existing file with\nstreams_xattr sets neither O_CREAT nor O_TRUNC, so it passes this check,\nand smb2_set_stream_name_xattr() then creates the stream. On a Time\nMachine share, opening a missing AFP_AfpInfo stream also writes one. A\nuser who can write a file at the filesystem level can therefore add\nstreams to it through a read-only share.\n\nDo not create a stream or synthesize AFP_AfpInfo when the share is not\nwritable. Existing streams still open normally, and a missing stream\nopened with FILE_OPEN still returns STATUS_OBJECT_NAME_NOT_FOUND.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-11-20 06:18:12","updated_at":"2026-11-20 06:18:12"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/09139429fab3a5114c18d7c15fb161511d4d66c9","name":"https://git.kernel.org/stable/c/09139429fab3a5114c18d7c15fb161511d4d66c9","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/ece35b45ec17a462cc5947ad4fbc3450657aa55b","name":"https://git.kernel.org/stable/c/ece35b45ec17a462cc5947ad4fbc3450657aa55b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99749","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99749","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 ece35b45ec17a462cc5947ad4fbc3450657aa55b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 09139429fab3a5114c18d7c15fb161511d4d66c9 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5.15","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 5.15 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":["fs/smb/server/smb2pdu.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"ece35b45ec17a462cc5947ad4fbc3450657aa55b","status":"affected","version":"e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9","versionType":"git"},{"lessThan":"09139429fab3a5114c18d7c15fb161511d4d66c9","status":"affected","version":"e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/smb/server/smb2pdu.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"5.15"},{"lessThan":"5.15","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":"5.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.4-rc2","versionStartIncluding":"5.15","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: enforce the read-only share flag when creating a stream\n\nWhen a share is read-only, smb2_open() rejects opens that would create\nor truncate a file. Creating a named stream on an existing file with\nstreams_xattr sets neither O_CREAT nor O_TRUNC, so it passes this check,\nand smb2_set_stream_name_xattr() then creates the stream. On a Time\nMachine share, opening a missing AFP_AfpInfo stream also writes one. A\nuser who can write a file at the filesystem level can therefore add\nstreams to it through a read-only share.\n\nDo not create a stream or synthesize AFP_AfpInfo when the share is not\nwritable. Existing streams still open normally, and a missing stream\nopened with FILE_OPEN still returns STATUS_OBJECT_NAME_NOT_FOUND."}],"providerMetadata":{"dateUpdated":"2026-11-20T05:51:19.794Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/ece35b45ec17a462cc5947ad4fbc3450657aa55b"},{"url":"https://git.kernel.org/stable/c/09139429fab3a5114c18d7c15fb161511d4d66c9"}],"title":"ksmbd: enforce the read-only share flag when creating a stream","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99749","datePublished":"2026-11-20T05:51:19.794Z","dateReserved":"2026-09-25T10:25:14.432Z","dateUpdated":"2026-11-20T05:51:19.794Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-20 06:18:12","lastModifiedDate":"2026-11-20 06:18:12","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99749","Ordinal":"1","Title":"ksmbd: enforce the read-only share flag when creating a stream","CVE":"CVE-2026-99749","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99749","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: enforce the read-only share flag when creating a stream\n\nWhen a share is read-only, smb2_open() rejects opens that would create\nor truncate a file. Creating a named stream on an existing file with\nstreams_xattr sets neither O_CREAT nor O_TRUNC, so it passes this check,\nand smb2_set_stream_name_xattr() then creates the stream. On a Time\nMachine share, opening a missing AFP_AfpInfo stream also writes one. A\nuser who can write a file at the filesystem level can therefore add\nstreams to it through a read-only share.\n\nDo not create a stream or synthesize AFP_AfpInfo when the share is not\nwritable. Existing streams still open normally, and a missing stream\nopened with FILE_OPEN still returns STATUS_OBJECT_NAME_NOT_FOUND.","Type":"Description","Title":"ksmbd: enforce the read-only share flag when creating a stream"}]}}}