p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in linux-gcp-fips · Seite 179

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für linux-gcp-fips: 794. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 7643

  1. CVE-2026-64496

    Hoch · CVSS 7.1EPSS 0,12%Korrektur verfügbar

    iio: event: Fix event FIFO reset race

    In the Linux kernel, the following vulnerability has been resolved: iio: event: Fix event FIFO reset race `iio_event_getfd()` creates the event file descriptor with `anon_inode_getfd()`, which allocates a new fd, creates the anonymous file and installs it in the process fd table before returning to the caller. The IIO code resets the event FIFO after `anon_inode_getfd()` has returned, but before `IIO_GET_EVENT_FD_IOCTL` has copied the fd number to userspace. But since fd tables are shared between threads, another thread can guess the newly allocated fd number and issue a `read()` on it as soon as the fd has been installed. This means the

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2026-64495

    Nicht bewertetEPSS 0,19%Korrektur verfügbar

    iio: gyro: bmg160: bail out when bandwidth/filter is not in table

    In the Linux kernel, the following vulnerability has been resolved: iio: gyro: bmg160: bail out when bandwidth/filter is not in table bmg160_get_filter() walks bmg160_samp_freq_table[] looking for the entry matching the bw_bits value read from the chip: for (i = 0; i < ARRAY_SIZE(bmg160_samp_freq_table); ++i) { if (bmg160_samp_freq_table[i].bw_bits == bw_bits) break; } *val = bmg160_samp_freq_table[i].filter; If no entry matches, i ends up equal to the array size and the next line reads one slot past the end. bmg160_set_filter() has the same shape, driven by 'val' instead of bw_bits. smatch flags both: drivers/iio/gyro/bmg160_

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2026-64494

    Nicht bewertetEPSS 0,18%Korrektur verfügbar

    iio: light: gp2ap002: fix runtime PM leak on read error

    In the Linux kernel, the following vulnerability has been resolved: iio: light: gp2ap002: fix runtime PM leak on read error gp2ap002_read_raw() calls pm_runtime_get_sync() before reading the lux value, but if gp2ap002_get_lux() fails, it returns directly. This skips the pm_runtime_put_autosuspend() call at the "out" label, permanently leaking a runtime PM reference and preventing the device from autosuspending. Replace the direct return with a "goto out" to ensure the reference is properly dropped on the error path.

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2026-64493

    Nicht bewertetEPSS 0,17%Korrektur verfügbar

    iio: pressure: mpl115: fix runtime PM leak on read error

    In the Linux kernel, the following vulnerability has been resolved: iio: pressure: mpl115: fix runtime PM leak on read error mpl115_read_raw() takes a runtime PM reference with pm_runtime_get_sync() before reading the processed pressure or raw temperature, but on the read error path it returns without calling pm_runtime_put_autosuspend(). Each failed read therefore leaks a runtime PM reference and prevents the device from autosuspending. Drop the reference before checking the return value so both the success and error paths are balanced.

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2026-64489

    Nicht bewertetEPSS 0,18%Korrektur verfügbar

    ALSA: ymfpci: check snd_ctl_new1() return value

    In the Linux kernel, the following vulnerability has been resolved: ALSA: ymfpci: check snd_ctl_new1() return value snd_ctl_new1() can return NULL when memory allocation fails. snd_ymfpci_create_spdif_controls() does not check the return value before dereferencing kctl->id.device, which can lead to a NULL pointer dereference. Add NULL checks after snd_ctl_new1() calls and return -ENOMEM if any fails.

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2026-64488

    Nicht bewertetEPSS 0,18%Korrektur verfügbar

    ALSA: aoa: check snd_ctl_new1() return value

    In the Linux kernel, the following vulnerability has been resolved: ALSA: aoa: check snd_ctl_new1() return value snd_ctl_new1() can return NULL when memory allocation fails. In layout.c, the function does not check the return value before dereferencing ctl->id.name or passing to aoa_snd_ctl_add(), which can lead to a NULL pointer dereference. Add NULL checks after snd_ctl_new1() calls and return early if any fails.

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2026-64487

    Nicht bewertetEPSS 0,18%Korrektur verfügbar

    ALSA: caiaq: fix out-of-bounds read in the Traktor Kontrol S4 input parser

    In the Linux kernel, the following vulnerability has been resolved: ALSA: caiaq: fix out-of-bounds read in the Traktor Kontrol S4 input parser snd_usb_caiaq_tks4_dispatch() decodes the Traktor Kontrol S4 input stream in fixed 16-byte (TKS4_MSGBLOCK_SIZE) message blocks. On every iteration it advances buf and subtracts the block size while looping on "while (len)". len is urb->actual_length. That value is supplied by the device and is not guaranteed to be a multiple of 16. When a final short block leaves len between 1 and 15, the loop runs once more, reads up to buf[15], and then does "len -= TKS4_MSGBLOCK_SIZE". As len is unsigned this und

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2026-64486

    Nicht bewertetEPSS 0,18%Korrektur verfügbar

    ALSA: cmipci: check snd_ctl_new1() return value

    In the Linux kernel, the following vulnerability has been resolved: ALSA: cmipci: check snd_ctl_new1() return value snd_ctl_new1() can return NULL when memory allocation fails. snd_cmipci_spdif_controls() does not check the return value before dereferencing kctl->id.device, which can lead to a NULL pointer dereference. Add NULL checks after snd_ctl_new1() calls and return -ENOMEM if any fails.

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2026-64484

    Nicht bewertetEPSS 0,18%Korrektur verfügbar

    ALSA: es1938: check snd_ctl_new1() return value

    In the Linux kernel, the following vulnerability has been resolved: ALSA: es1938: check snd_ctl_new1() return value snd_ctl_new1() can return NULL when memory allocation fails. snd_es1938_mixer() does not check the return value before dereferencing the pointer, which can lead to a NULL pointer dereference. Add a NULL check after snd_ctl_new1() and return -ENOMEM if it fails.

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  10. CVE-2026-64483

    Nicht bewertetEPSS 0,18%Korrektur verfügbar

    ALSA: firewire: isight: bound the sample count to the packet payload

    In the Linux kernel, the following vulnerability has been resolved: ALSA: firewire: isight: bound the sample count to the packet payload isight_packet() takes the frame count from the device iso packet and checks it only against the device claimed iso length. count = be32_to_cpu(payload->sample_count); if (likely(count <= (length - 16) / 4)) isight_samples(isight, payload->samples, count); length is the iso header data_length. It can be up to 0xffff. So the gate allows a count up to about 16379. isight_samples() then copies count frames out of payload->samples into the PCM DMA buffer. payload->samples holds only 2 * MAX_FRAMES_PER_PA

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2026-64482

    Nicht bewertetEPSS 0,18%Korrektur verfügbar

    ALSA: gus: check snd_ctl_new1() return value

    In the Linux kernel, the following vulnerability has been resolved: ALSA: gus: check snd_ctl_new1() return value snd_ctl_new1() can return NULL when memory allocation fails. snd_gf1_pcm_volume_control() does not check the return value before dereferencing kctl->id.index, which can lead to a NULL pointer dereference. Add a NULL check after snd_ctl_new1() and return -ENOMEM if it fails.

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2026-64481

    Hoch · CVSS 7.8EPSS 0,18%Korrektur verfügbar

    ALSA: hda/cs35l41: Fix firmware load work teardown

    In the Linux kernel, the following vulnerability has been resolved: ALSA: hda/cs35l41: Fix firmware load work teardown cs35l41_hda creates ALSA controls whose private data points at the cs35l41_hda object. The firmware load control can also queue fw_load_work. Those controls are not removed on component unbind, and device remove only cancels fw_load_work through cs35l41_remove_dsp(). That helper is skipped when halo_initialized is false. With firmware_autostart disabled, a firmware load can be requested before the DSP has been initialized. If the component or device is removed before the queued work runs, the worker can run after teardown

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  13. CVE-2026-64480

    Nicht bewertetEPSS 0,18%Korrektur verfügbar

    ALSA: ice1712: check snd_ctl_new1() return value

    In the Linux kernel, the following vulnerability has been resolved: ALSA: ice1712: check snd_ctl_new1() return value snd_ctl_new1() can return NULL when memory allocation fails. The ice1712 driver calls snd_ctl_new1() without checking the return value before dereferencing the pointer in multiple places (ice1712.c, ice1724.c, aureon.c), which can lead to NULL pointer dereferences. Add NULL checks after snd_ctl_new1() calls and return -ENOMEM if any fails.

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  14. CVE-2026-64479

    Nicht bewertetEPSS 0,18%Korrektur verfügbar

    ALSA: seq: Fix uninitialised heap leak in snd_seq_event_dup()

    In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: Fix uninitialised heap leak in snd_seq_event_dup() snd_seq_event_dup() copies an incoming event into a pool cell and, in the UMP-enabled build, clears the trailing cell->ump.raw.extra word that the memcpy() did not cover. The guard deciding whether to clear it compares the copied size against sizeof(cell->event): memcpy(&cell->ump, event, size); if (size < sizeof(cell->event)) cell->ump.raw.extra = 0; For a legacy (non-UMP) event, size == sizeof(struct snd_seq_event) == sizeof(cell->event), so the condition is false and the extra word keeps stale data. Th

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  15. CVE-2026-64478

    Nicht bewertetEPSS 0,18%Korrektur verfügbar

    ALSA: usb-audio: avoid kobject path lookup in DualSense match

    In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: avoid kobject path lookup in DualSense match The DualSense jack-detection input handler verifies that a matching input device belongs to the same physical controller by building kobject path strings for both the input device and the USB audio device, then comparing the path prefix. This was observed when a weak physical connection caused the controller to rapidly disconnect and reconnect. During that repeated hotplug, snd_dualsense_ih_match() can run while the controller's USB device is being disconnected. kobject_get_path() walks ancestor kobjects and der

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  16. CVE-2026-64476

    Nicht bewertetEPSS 0,18%Korrektur verfügbar

    vfio/pci: Latch disable_idle_d3 per device

    In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Latch disable_idle_d3 per device When disable_idle_d3 was introduced in vfio-pci, it directly manipulated the device power state with pci_set_power_state(). There were no refcounts to maintain or balanced operations, we could unconditionally bring the device to D0 and conditionally move it to D3hot. Therefore the module parameter was made writable. Later, in commit c61302aa48f7 ("vfio/pci: Move module parameters to vfio_pci.c"), as part of the vfio-pci-core split, the writable aspect of the module parameter was nullified. The parameter value could still be cha

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  17. CVE-2026-64475

    Hoch · CVSS 8.8EPSS 0,14%Korrektur verfügbar

    vfio/pci: Release the VGA arbiter client on register_device() failure

    In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Release the VGA arbiter client on register_device() failure The re-order in the Fixes commit below displaced vfio_pci_vga_init() as the last failure point of what is now vfio_pci_core_register_device() without introducing an unwind for the VGA arbiter registration. In current kernels this is mostly benign because vfio_pci_set_decode() only uses pci_dev state, but the original failure path could leave a callback with a freed vdev cookie. The stale registration also becomes unsafe again once the callback follows drvdata to the vfio device. Add the required VGA un

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  18. CVE-2026-64474

    Nicht bewertetEPSS 0,18%Korrektur verfügbar

    vfio: prevent infinite loop in vfio_mig_get_next_state() on blocked arc

    In the Linux kernel, the following vulnerability has been resolved: vfio: prevent infinite loop in vfio_mig_get_next_state() on blocked arc vfio_mig_get_next_state() walks vfio_from_fsm_table[] one step at a time, looping to skip optional states the device does not support until *next_fsm is supported. A blocked transition is encoded as VFIO_DEVICE_STATE_ERROR, which the trailing return reports as -EINVAL. The skip loop does not account for the ERROR sentinel. state_flags_table[ERROR] is ~0U and vfio_from_fsm_table[ERROR][*] is ERROR, so once *next_fsm becomes ERROR the loop condition stays true and *next_fsm never changes. The blocked arc

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  19. CVE-2026-64473

    Nicht bewertetEPSS 0,18%Korrektur verfügbar

    vfio: Remove device debugfs before releasing devres

    In the Linux kernel, the following vulnerability has been resolved: vfio: Remove device debugfs before releasing devres VFIO device debugfs files created with debugfs_create_devm_seqfile() store a devres allocated debugfs_devm_entry as inode private data. vfio_unregister_group_dev() currently calls vfio_device_del() before vfio_device_debugfs_exit(), but device_del() releases devres. This can leave debugfs entries visible with stale inode private data while unregister waits for userspace references to drain. Remove the per-device debugfs tree before vfio_device_del(). The debugfs view is diagnostic only, so losing it at the start of unre

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert
  20. CVE-2026-64472

    Nicht bewertetEPSS 0,18%Korrektur verfügbar

    vfio/mlx5: Fix racy bitfields and tighten struct layout

    In the Linux kernel, the following vulnerability has been resolved: vfio/mlx5: Fix racy bitfields and tighten struct layout Bitfield operations are not atomic, they use a read-modify-write pattern, therefore we should be careful not to pack bitfields that can be concurrently updated into the same storage unit. This split takes a binary approach: flags that are only modified pre/post open/close remain bitfields, flags modified from user action, including actions that reach across to another device (ex. reset) use dedicated storage units. Note mlx5_vhca_page_tracker.status is relocated to fill the alignment hole this split exposes. Bitfiel

    • Auf 6.8.0-1071.79+fips1 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →