{"api_version":"1","generated_at":"2026-09-22T05:02:29+00:00","cve":"CVE-2026-90337","urls":{"html":"https://cve.report/CVE-2026-90337","api":"https://cve.report/api/cve/CVE-2026-90337.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-90337","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-90337"},"summary":{"title":"serial: core: do fallible allocations before the console can be registered","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nserial: core: do fallible allocations before the console can be registered\n\nserial_core_add_one_port() allocates uport->tty_groups after\nuart_configure_port(), which may register the console. If the allocation\nfails, the driver unwinds the port while its console remains registered.\nThe earlier uport->name allocation has a related failure path that leaves\nstate->uart_port linked to a port being freed.\n\nFailslab reproduced a NULL dereference in PL011 console output and a KASAN\nuse-after-free in i.MX console output after failed binds.\n\nAllocate the name and tty_groups before linking the port and configuring\nit. Reserve space for the optional driver attribute group because\nconfig_port() may populate uport->attr_group during configuration.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-17 17:17:32","updated_at":"2026-09-17 17:17:32"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/c2aec15f78b2e6ccd9b94216a901248511355982","name":"https://git.kernel.org/stable/c/c2aec15f78b2e6ccd9b94216a901248511355982","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/1a0e4fbce5d9c1bc179a35a2fd9ed142664299e3","name":"https://git.kernel.org/stable/c/1a0e4fbce5d9c1bc179a35a2fd9ed142664299e3","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-90337","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90337","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 266dcff03eed0050b6af11aaf2a61ab837d7ba3f c2aec15f78b2e6ccd9b94216a901248511355982 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 266dcff03eed0050b6af11aaf2a61ab837d7ba3f 1a0e4fbce5d9c1bc179a35a2fd9ed142664299e3 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3.17","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 3.17 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":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/tty/serial/serial_core.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"c2aec15f78b2e6ccd9b94216a901248511355982","status":"affected","version":"266dcff03eed0050b6af11aaf2a61ab837d7ba3f","versionType":"git"},{"lessThan":"1a0e4fbce5d9c1bc179a35a2fd9ed142664299e3","status":"affected","version":"266dcff03eed0050b6af11aaf2a61ab837d7ba3f","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/tty/serial/serial_core.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"3.17"},{"lessThan":"3.17","status":"unaffected","version":"0","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":"7.2.6","versionStartIncluding":"3.17","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"3.17","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nserial: core: do fallible allocations before the console can be registered\n\nserial_core_add_one_port() allocates uport->tty_groups after\nuart_configure_port(), which may register the console. If the allocation\nfails, the driver unwinds the port while its console remains registered.\nThe earlier uport->name allocation has a related failure path that leaves\nstate->uart_port linked to a port being freed.\n\nFailslab reproduced a NULL dereference in PL011 console output and a KASAN\nuse-after-free in i.MX console output after failed binds.\n\nAllocate the name and tty_groups before linking the port and configuring\nit. Reserve space for the optional driver attribute group because\nconfig_port() may populate uport->attr_group during configuration."}],"providerMetadata":{"dateUpdated":"2026-09-17T16:08:49.687Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/c2aec15f78b2e6ccd9b94216a901248511355982"},{"url":"https://git.kernel.org/stable/c/1a0e4fbce5d9c1bc179a35a2fd9ed142664299e3"}],"title":"serial: core: do fallible allocations before the console can be registered","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-90337","datePublished":"2026-09-17T16:08:49.687Z","dateReserved":"2026-09-11T19:38:34.804Z","dateUpdated":"2026-09-17T16:08:49.687Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-17 17:17:32","lastModifiedDate":"2026-09-17 17:17:32","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"90337","Ordinal":"1","Title":"serial: core: do fallible allocations before the console can be ","CVE":"CVE-2026-90337","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"90337","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nserial: core: do fallible allocations before the console can be registered\n\nserial_core_add_one_port() allocates uport->tty_groups after\nuart_configure_port(), which may register the console. If the allocation\nfails, the driver unwinds the port while its console remains registered.\nThe earlier uport->name allocation has a related failure path that leaves\nstate->uart_port linked to a port being freed.\n\nFailslab reproduced a NULL dereference in PL011 console output and a KASAN\nuse-after-free in i.MX console output after failed binds.\n\nAllocate the name and tty_groups before linking the port and configuring\nit. Reserve space for the optional driver attribute group because\nconfig_port() may populate uport->attr_group during configuration.","Type":"Description","Title":"serial: core: do fallible allocations before the console can be "}]}}}