p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Schwachstellen im Stack Betriebssysteme · Seite 42

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für Betriebssysteme: 6603. Davon im KEV-Katalog: 4.

Sicherheitslücken filtern
Betriebssysteme

Sicherheitslücken: 160200

  1. CVE-2026-116816

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

    llama.cpp b5899 before b10261 Heap Out-of-Bounds Write via plamo2 Tokenizer

    llama.cpp b5899 before b10261 contains a heap out-of-bounds write vulnerability in llm_tokenizer_plamo2::build that allows attackers to corrupt heap memory via crafted GGUF models. Attackers can supply BYTE-typed token text like <0x-1> whose negative parsed value writes token ids before the bytes_ buffer during model loading, causing crashes or potential code execution.

    • Auf 10271+dfsg-1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2025-71439

    Mittel · CVSS 6.8EPSS 0,12%Keine Korrektur veröffentlicht

    llama.cpp before b5649 Heap Out-of-Bounds Read via llama_vocab::impl::print_info

    llama.cpp before b5649 contains a heap out-of-bounds read vulnerability in llama_vocab::impl::print_info() that allows attackers to crash model loading via oversized special token IDs. Attackers can supply a crafted GGUF model with a short tokenizer.ggml.tokens array, causing llama-cli or llama-server to read past id_to_token and crash.

    Veröffentlicht Aktualisiert
  3. CVE-2024-58400

    Hoch · CVSS 8.8EPSS 0,42%Keine Korrektur veröffentlicht

    llama.cpp before b3701 Out-of-Bounds Read in llama_decode via Token IDs

    llama.cpp before b3701 contains an out-of-bounds read vulnerability in llama_decode_internal and llama_encode_internal that allows remote unauthenticated attackers to read memory by supplying unvalidated token IDs. Attackers can send integer-array prompts to the llama-server /completion endpoint with IDs outside 0 to n_vocab to read embedding memory out of bounds or crash the process.

    Veröffentlicht Aktualisiert
  4. CVE-2024-58399

    Mittel · CVSS 6.9EPSS 0,12%Keine Korrektur veröffentlicht

    llama.cpp before b2731 Out-of-Bounds Read via GGUF Tensor Offsets

    llama.cpp before b2731 contains an out-of-bounds read vulnerability in llama_model_loader that allows attackers to read memory outside the mapped model file via crafted GGUF tensor offsets. Attackers can supply a crafted or truncated GGUF model file with arbitrary 64-bit tensor offsets to crash the process or load adjacent process memory as model weights.

    Veröffentlicht Aktualisiert
  5. CVE-2026-116620

    Mittel · CVSS 6.9EPSS 0,3%Keine Korrektur veröffentlicht

    Tencent RapidJSON Regex stream.h Take out-of-bounds

    A security vulnerability has been detected in Tencent RapidJSON up to 1.1.0. This issue affects the function GenericStringStream<UTF8<char>>::Take in the library include/rapidjson/stream.h of the component Regex Parser. The manipulation leads to out-of-bounds read. The attack can be initiated remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.

    Veröffentlicht Aktualisiert
  6. RLSA-2026:89082

    Hoch · CVSS 8.8Korrektur verfügbar

    Important: kernel-rt security, bug fix, and enhancement update

    The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements. Security Fix(es): * kernel: tcp: restrict SO_ATTACH_FILTER to priv users (CVE-2026-53236) * kernel: fuse: re-lock request before replacing page cache folio (CVE-2026-53388) * kernel: writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() (CVE-2026-64378) * kernel: net: gro: fix double aggregation of flush-marked skbs (CVE-2026-68136) * kernel: net/packet: avoid fanout hook re-registration after unregister (CVE-2026-68338) * kernel: net/iucv: fix use-after-free of a severed

    • Auf 0:4.18.0-553.178.1.rt7.519.el8_10 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 →