https://vulnerability.circl.lu/rss/recent/all/10 Most recent entries from all 2026-09-28T17:59:23.627894+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent entries. https://vulnerability.circl.lu/vuln/bell-cve-2026-93276 BELL-CVE-2026-93276 2026-09-28T17:59:23.644371+00:00

Affected: Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts

 https://vulnerability.circl.lu/vuln/fkie_cve-2026-93276 fkie_cve-2026-93276 2026-09-28T17:59:23.644501+00:00

In the Linux kernel, the following vulnerability has been resolved:

phy: renesas: phy-rcar-gen3-usb2: Fix devm action registration for disabled VBUS regulator

devm_regulator_get_exclusive() initialises the regulator with enable_count = 1, requiring the consumer to disable it before release.

The devm disable action was previously only registered when the caller explicitly requested enable, so when the regulator was left in its initial enabled state without an explicit enable call, the cleanup path skipped decrementing enable_count, triggering a WARN_ON during regulator release on device removal.

Fix this by always registering the devm disable action based on the actual enabled state via regulator_is_enabled(), regardless of whether the caller requested an explicit enable. This covers both the explicitly enabled case and the initial state set by devm_regulator_get_exclusive().

 https://vulnerability.circl.lu/vuln/ghsa-gfvh-9676-44ch GHSA-gfvh-9676-44ch 2026-09-28T17:59:23.644578+00:00

In the Linux kernel, the following vulnerability has been resolved:

phy: renesas: phy-rcar-gen3-usb2: Fix devm action registration for disabled VBUS regulator

devm_regulator_get_exclusive() initialises the regulator with enable_count = 1, requiring the consumer to disable it before release.

The devm disable action was previously only registered when the caller explicitly requested enable, so when the regulator was left in its initial enabled state without an explicit enable call, the cleanup path skipped decrementing enable_count, triggering a WARN_ON during regulator release on device removal.

Fix this by always registering the devm disable action based on the actual enabled state via regulator_is_enabled(), regardless of whether the caller requested an explicit enable. This covers both the explicitly enabled case and the initial state set by devm_regulator_get_exclusive().

 https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-93276 UBUNTU-CVE-2026-93276 2026-09-28T17:59:23.644623+00:00

Affected: Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more

In the Linux kernel, the following vulnerability has been resolved: phy: renesas: phy-rcar-gen3-usb2: Fix devm action registration for disabled VBUS regulator devm_regulator_get_exclusive() initialises the regulator with enable_count = 1, requiring the consumer to disable it before release. The devm disable action was previously only registered when the caller explicitly requested enable, so when the regulator was left in its initial enabled state without an explicit enable call, the cleanup path skipped decrementing enable_count, triggering a WARN_ON during regulator release on device removal. Fix this by always registering the devm disable action based on the actual enabled state via regulator_is_enabled(), regardless of whether the caller requested an explicit enable. This covers both the explicitly enabled case and the initial state set by devm_regulator_get_exclusive().

 https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579 WID-SEC-W-2026-3579 — Linux Kernel: Mehrere Schwachstellen 2026-09-28T17:59:23.645052+00:00

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.