FKIE_CVE-2026-99455

Vulnerability from fkie_nvd - Published: 2026-11-19 15:17 - Updated: 2026-11-19 15:17
Severity
Summary
In the Linux kernel, the following vulnerability has been resolved: serial: core: shut down initialized port on removal When a serial port configured as a console is opened and subsequently closed, tty_port_shutdown() skips invoking port->ops->shutdown() because port->console is true. As a result, tty_port_initialized() remains true and the port's interrupt handler stays registered in the irq subsystem. If the underlying device is later unbound or removed (e.g. via sysfs driver unbind or device hot-unplug), serial_core_remove_one_port() unregisters the console, frees uport->name via kfree(), and tears down the port without shutting it down or freeing its IRQ. Consequently, the irqaction descriptor remains registered in genirq with action->name pointing to freed memory. This triggers a use-after-free read whenever genirq accesses action->name, such as when reading /proc/interrupts: BUG: KASAN: slab-use-after-free in string+0x476/0x570 Call Trace: string+0x476/0x570 vsnprintf+0x422/0x1300 seq_printf+0x... show_interrupts+... Fix this by acquiring port->mutex in serial_core_remove_one_port() after console unregistration, clearing port->console under the mutex to prevent data races with concurrent tty_port_shutdown(), and invoking uart_shutdown(NULL, state) if the port remains initialized. This ensures that port->ops->shutdown() is called and the IRQ is freed before kfree(uport->name).
Impacted products
Vendor Product Version

{
  "affected": [
    {
      "affectedData": [
        {
          "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": "b05d5ed61e84ad15536e4e51db79a1d1c221c6f1",
              "status": "affected",
              "version": "761ed4a94582ab291aa24dcbea4e01e8936488c8",
              "versionType": "git"
            },
            {
              "lessThan": "0f332cce4d592d751aad89b404f68463099167c8",
              "status": "affected",
              "version": "761ed4a94582ab291aa24dcbea4e01e8936488c8",
              "versionType": "git"
            },
            {
              "lessThan": "928335263daf58e8c0e14d860091e57791693ea0",
              "status": "affected",
              "version": "761ed4a94582ab291aa24dcbea4e01e8936488c8",
              "versionType": "git"
            },
            {
              "lessThan": "810d467c11f0c85107874d08dfdd11acba6aa0c0",
              "status": "affected",
              "version": "761ed4a94582ab291aa24dcbea4e01e8936488c8",
              "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": "4.9"
            },
            {
              "lessThan": "4.9",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.117",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.61",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.3.*",
              "status": "unaffected",
              "version": "7.3.2",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.4-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nserial: core: shut down initialized port on removal\n\nWhen a serial port configured as a console is opened and subsequently\nclosed, tty_port_shutdown() skips invoking port-\u003eops-\u003eshutdown() because\nport-\u003econsole is true. As a result, tty_port_initialized() remains true\nand the port\u0027s interrupt handler stays registered in the irq subsystem.\n\nIf the underlying device is later unbound or removed (e.g. via sysfs\ndriver unbind or device hot-unplug), serial_core_remove_one_port()\nunregisters the console, frees uport-\u003ename via kfree(), and tears down\nthe port without shutting it down or freeing its IRQ. Consequently, the\nirqaction descriptor remains registered in genirq with action-\u003ename\npointing to freed memory.\n\nThis triggers a use-after-free read whenever genirq accesses action-\u003ename,\nsuch as when reading /proc/interrupts:\n\n  BUG: KASAN: slab-use-after-free in string+0x476/0x570\n  Call Trace:\n   string+0x476/0x570\n   vsnprintf+0x422/0x1300\n   seq_printf+0x...\n   show_interrupts+...\n\nFix this by acquiring port-\u003emutex in serial_core_remove_one_port() after\nconsole unregistration, clearing port-\u003econsole under the mutex to prevent\ndata races with concurrent tty_port_shutdown(), and invoking\nuart_shutdown(NULL, state) if the port remains initialized. This ensures\nthat port-\u003eops-\u003eshutdown() is called and the IRQ is freed before\nkfree(uport-\u003ename)."
    }
  ],
  "id": "CVE-2026-99455",
  "lastModified": "2026-11-19T15:17:59.453",
  "metrics": {},
  "published": "2026-11-19T15:17:59.453",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/0f332cce4d592d751aad89b404f68463099167c8"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/810d467c11f0c85107874d08dfdd11acba6aa0c0"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/928335263daf58e8c0e14d860091e57791693ea0"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/b05d5ed61e84ad15536e4e51db79a1d1c221c6f1"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.