https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T17:01:13.576090+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bell-cve-2026-31535 BELL-CVE-2026-31535 2026-10-03T17:01:13.681535+00:00

Affected: Alpaquita:stream: linux-lts

 https://cve.radiocsirt.org/vuln/euvd-2026-315609 EUVD-2026-315609 2026-10-03T17:01:13.681582+00:00 EUVD-2026-315609 https://cve.radiocsirt.org/vuln/fkie_cve-2026-31535 fkie_cve-2026-31535 2026-10-03T17:01:13.681597+00:00

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

smb: client: make use of smbdirect_socket.recv_io.credits.available

The logic off managing recv credits by counting posted recv_io and granted credits is racy.

That's because the peer might already consumed a credit, but between receiving the incoming recv at the hardware and processing the completion in the 'recv_done' functions we likely have a window where we grant credits, which don't really exist.

So we better have a decicated counter for the available credits, which will be incremented when we posted new recv buffers and drained when we grant the credits to the peer.

 https://cve.radiocsirt.org/vuln/ghsa-4w64-3hfc-pgqc GHSA-4w64-3hfc-pgqc 2026-10-03T17:01:13.681629+00:00

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

smb: client: make use of smbdirect_socket.recv_io.credits.available

The logic off managing recv credits by counting posted recv_io and granted credits is racy.

That's because the peer might already consumed a credit, but between receiving the incoming recv at the hardware and processing the completion in the 'recv_done' functions we likely have a window where we grant credits, which don't really exist.

So we better have a decicated counter for the available credits, which will be incremented when we posted new recv buffers and drained when we grant the credits to the peer.

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31535 UBUNTU-CVE-2026-31535 2026-10-03T17:01:13.681652+00:00

Affected: Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 85 more

In the Linux kernel, the following vulnerability has been resolved: smb: client: make use of smbdirect_socket.recv_io.credits.available The logic off managing recv credits by counting posted recv_io and granted credits is racy. That's because the peer might already consumed a credit, but between receiving the incoming recv at the hardware and processing the completion in the 'recv_done' functions we likely have a window where we grant credits, which don't really exist. So we better have a decicated counter for the available credits, which will be incremented when we posted new recv buffers and drained when we grant the credits to the peer.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1279 WID-SEC-W-2026-1279 — Linux Kernel: Mehrere Schwachstellen 2026-10-03T17:01:13.681800+00:00

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, welche zu einem Denial-of-Service-Zustand, einer Rechteausweitung, der Ausführung von Code oder einer Speicherbeschädigung führen könnten.