From: Ulrich Hecht <uli@fpond.eu>
To: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"pavel@nabladev.com" <pavel@nabladev.com>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
"masami.ichikawa@cybertrust.co.jp"
<masami.ichikawa@cybertrust.co.jp>,
"chris.paterson2@renesas.com" <chris.paterson2@renesas.com>,
"nobuhiro.iwamatsu.x90@mail.toshiba"
<nobuhiro.iwamatsu.x90@mail.toshiba>
Subject: [ANNOUNCE] Release v4.19.325-cip130
Date: Wed, 11 Mar 2026 09:23:24 +0100 (CET) [thread overview]
Message-ID: <1080195231.96465.1773217404718@webmail.strato.de> (raw)
Hi,
the CIP kernel team has released Linux kernel v4.19.325-cip130. The linux-4.19.y-cip tree's base version has been updated to v4.19-st14. The trees are up-to-date with kernel 5.10.251.
You can get this release via the git tree or as a tarball from https://mirrors.edge.kernel.org/pub/linux/kernel/projects/cip/4.19/
v4.19.325-cip130:
repository:
https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
branch:
linux-4.19.y-cip
commit hash:
ef917a8bed27ab284a27aa2e8e242bab707d7aa3
Fixed CVEs:
CVE-2022-50516: fs: dlm: fix invalid derefence of sb_lvbptr
CVE-2025-71232: scsi: qla2xxx: Free sp in error path to fix system crash
CVE-2025-71235: scsi: qla2xxx: Delay module unload while fabric scan in progress
CVE-2025-71236: scsi: qla2xxx: Validate sp before freeing associated memory
CVE-2025-71237: nilfs2: Fix potential block overflow that cause system hang
CVE-2025-71238: scsi: qla2xxx: Fix bsg_done() causing double free
CVE-2026-23222: crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly
CVE-2026-23229: crypto: virtio - Add spinlock protection with virtqueue notification
CVE-2026-23234: f2fs: fix to avoid UAF in f2fs_write_end_io()
CVE-2026-23235: f2fs: fix out-of-bounds access in sysfs attribute read/write
CVE-2026-23237: platform/x86: classmate-laptop: Add missing NULL pointer checks
Best regards,
Ulrich Hecht
reply other threads:[~2026-03-11 8:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1080195231.96465.1773217404718@webmail.strato.de \
--to=uli@fpond.eu \
--cc=chris.paterson2@renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.com \
--cc=masami.ichikawa@cybertrust.co.jp \
--cc=nobuhiro.iwamatsu.x90@mail.toshiba \
--cc=pavel@nabladev.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox