{"api_version":"1","generated_at":"2026-09-22T05:02:46+00:00","cve":"CVE-2026-93134","urls":{"html":"https://cve.report/CVE-2026-93134","api":"https://cve.report/api/cve/CVE-2026-93134.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-93134","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-93134"},"summary":{"title":"printk: Fix possible console use-after-free","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nprintk: Fix possible console use-after-free\n\nWhen emitting a record via legacy printing, it is possible that a handover\nto another legacy printing context occurs. When a context has performed a\nhandover, the console SRCU read lock is released and the pointer to the\nconsole struct might now be invalid. Therefore, after calling\nnbcon_legacy_emit_next_record() or console_emit_next_record(), it is\nnecessary to check if a handover occurred _before_ further @con usage.\n\nSashiko pointed out that console_flush_one_record() was not doing this.\n\nIn console_flush_one_record(), after emitting a record, move the further\nusage of @con after the handover check.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-17 17:18:08","updated_at":"2026-09-17 17:18:08"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/8f194dee0c0d1223255bae1429e1939882f540fc","name":"https://git.kernel.org/stable/c/8f194dee0c0d1223255bae1429e1939882f540fc","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/f0104a7b730de32eefb3d4a27279592b5504ad59","name":"https://git.kernel.org/stable/c/f0104a7b730de32eefb3d4a27279592b5504ad59","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/fbf9bb81b21537ede387a31cc586f1d2ce66a74e","name":"https://git.kernel.org/stable/c/fbf9bb81b21537ede387a31cc586f1d2ce66a74e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/36630cafbeede0b64c370edb2f7b4094327ee1e0","name":"https://git.kernel.org/stable/c/36630cafbeede0b64c370edb2f7b4094327ee1e0","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-93134","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93134","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected c158834b223fbfab3a14855ac203b8d9cddbbefd f0104a7b730de32eefb3d4a27279592b5504ad59 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected c158834b223fbfab3a14855ac203b8d9cddbbefd fbf9bb81b21537ede387a31cc586f1d2ce66a74e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected c158834b223fbfab3a14855ac203b8d9cddbbefd 8f194dee0c0d1223255bae1429e1939882f540fc git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected c158834b223fbfab3a14855ac203b8d9cddbbefd 36630cafbeede0b64c370edb2f7b4094327ee1e0 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.12","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.110 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.52 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.6 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"93134","cve":"CVE-2026-93134","epss":"0.002000000","percentile":"0.101610000","score_date":"2026-09-18","updated_at":"2026-09-19 00:06:17"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["kernel/printk/printk.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"f0104a7b730de32eefb3d4a27279592b5504ad59","status":"affected","version":"c158834b223fbfab3a14855ac203b8d9cddbbefd","versionType":"git"},{"lessThan":"fbf9bb81b21537ede387a31cc586f1d2ce66a74e","status":"affected","version":"c158834b223fbfab3a14855ac203b8d9cddbbefd","versionType":"git"},{"lessThan":"8f194dee0c0d1223255bae1429e1939882f540fc","status":"affected","version":"c158834b223fbfab3a14855ac203b8d9cddbbefd","versionType":"git"},{"lessThan":"36630cafbeede0b64c370edb2f7b4094327ee1e0","status":"affected","version":"c158834b223fbfab3a14855ac203b8d9cddbbefd","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["kernel/printk/printk.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.12"},{"lessThan":"6.12","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.110","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.52","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.6","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.110","versionStartIncluding":"6.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.52","versionStartIncluding":"6.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.6","versionStartIncluding":"6.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"6.12","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nprintk: Fix possible console use-after-free\n\nWhen emitting a record via legacy printing, it is possible that a handover\nto another legacy printing context occurs. When a context has performed a\nhandover, the console SRCU read lock is released and the pointer to the\nconsole struct might now be invalid. Therefore, after calling\nnbcon_legacy_emit_next_record() or console_emit_next_record(), it is\nnecessary to check if a handover occurred _before_ further @con usage.\n\nSashiko pointed out that console_flush_one_record() was not doing this.\n\nIn console_flush_one_record(), after emitting a record, move the further\nusage of @con after the handover check."}],"providerMetadata":{"dateUpdated":"2026-09-17T16:11:36.077Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/f0104a7b730de32eefb3d4a27279592b5504ad59"},{"url":"https://git.kernel.org/stable/c/fbf9bb81b21537ede387a31cc586f1d2ce66a74e"},{"url":"https://git.kernel.org/stable/c/8f194dee0c0d1223255bae1429e1939882f540fc"},{"url":"https://git.kernel.org/stable/c/36630cafbeede0b64c370edb2f7b4094327ee1e0"}],"title":"printk: Fix possible console use-after-free","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-93134","datePublished":"2026-09-17T16:11:36.077Z","dateReserved":"2026-09-17T16:02:15.087Z","dateUpdated":"2026-09-17T16:11:36.077Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-17 17:18:08","lastModifiedDate":"2026-09-17 17:18:08","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"93134","Ordinal":"1","Title":"printk: Fix possible console use-after-free","CVE":"CVE-2026-93134","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"93134","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nprintk: Fix possible console use-after-free\n\nWhen emitting a record via legacy printing, it is possible that a handover\nto another legacy printing context occurs. When a context has performed a\nhandover, the console SRCU read lock is released and the pointer to the\nconsole struct might now be invalid. Therefore, after calling\nnbcon_legacy_emit_next_record() or console_emit_next_record(), it is\nnecessary to check if a handover occurred _before_ further @con usage.\n\nSashiko pointed out that console_flush_one_record() was not doing this.\n\nIn console_flush_one_record(), after emitting a record, move the further\nusage of @con after the handover check.","Type":"Description","Title":"printk: Fix possible console use-after-free"}]}}}