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-cip131
Date: Sun, 12 Apr 2026 09:37:16 +0200 (CEST) [thread overview]
Message-ID: <459507685.15146.1775979436923@webmail.strato.de> (raw)
Hi,
the CIP kernel team has released Linux kernel v4.19.325-cip131. The linux-4.19.y-cip tree's base version has been updated to v4.19-st15. The trees are up-to-date with kernel 5.10.252.
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-cip131:
repository:
https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
branch:
linux-4.19.y-cip
commit hash:
7aeff6c7984c582f96916d12bd33eefbd746459c
Fixed CVEs:
CVE-2025-39889: Bluetooth: l2cap: Check encryption key size on incoming connection
CVE-2025-71239: audit: add fchmodat2() to change attributes class
CVE-2026-23241: audit: add missing syscalls to read class
CVE-2026-23243: RDMA/umad: Reject negative data_len in ib_umad_write
CVE-2026-23273: macvlan: observe an RCU grace period in macvlan_common_newlink() error path
CVE-2026-31411: net: atm: fix crash due to unvalidated vcc pointer in sigd_send()
Best regards,
Ulrich Hecht
next reply other threads:[~2026-04-12 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-12 7:37 Ulrich Hecht [this message]
2026-04-13 5:36 ` [ANNOUNCE] Release v4.19.325-cip131 Jan Kiszka
2026-04-13 8:17 ` [cip-dev] " Ulrich Hecht
2026-04-13 10:08 ` Jan Kiszka
2026-04-13 11:29 ` Pavel Machek
2026-04-13 15:47 ` Jan Kiszka
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=459507685.15146.1775979436923@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