public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Ulrich Hecht <uli@fpond.eu>
To: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
	"pavel@denx.de" <pavel@denx.de>,
	"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>,
	"nobuhiro1.iwamatsu@toshiba.co.jp"
	<nobuhiro1.iwamatsu@toshiba.co.jp>
Subject: [ANNOUNCE] Release v4.19.325-cip120
Date: Thu, 8 May 2025 13:56:53 +0200 (CEST)	[thread overview]
Message-ID: <2829441.388422.1746705413499@webmail.strato.de> (raw)

Hi,

the CIP kernel team has released Linux kernel v4.19.325-cip120. The linux-4.19.y-cip tree's base version has been updated to v4.19-st4. The trees are up-to-date with kernel 5.4.292.

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-cip120:
    repository:
      https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
    branch:
      linux-4.19.y-cip
    commit hash:
      33b79fc4625daef9e71c91db90a0808d2bc1ae23
    Fixed CVEs:
      CVE-2025-21638: sctp: sysctl: auth_enable: avoid using current->nsproxy
      CVE-2025-21640: sctp: sysctl: cookie_hmac_alg: avoid using current->nsproxy
      CVE-2025-21956: drm/amd/display: Assign normalized_pix_clk when color depth = 14
      CVE-2025-21959: netfilter: nf_conncount: Fully initialize struct nf_conncount_tuple in insert_tree()
      CVE-2025-21991: x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes
      CVE-2025-21992: HID: ignore non-functional sensor in HP 5MP Camera
      CVE-2025-21996: drm/radeon: fix uninitialized size issue in radeon_vce_cs_parse()
      CVE-2025-22004: net: atm: fix use after free in lec_send()
      CVE-2025-22007: Bluetooth: Fix error code in chan_alloc_skb_cb()
      CVE-2023-53034: ntb_hw_switchtec: Fix shift-out-of-bounds in switchtec_ntb_mw_set_trans
      CVE-2025-21971: net_sched: Prevent creation of classes with TC_H_ROOT
      CVE-2025-21993: iscsi_ibft: Fix UBSAN shift-out-of-bounds warning in ibft_attr_show_nic()
      CVE-2025-22018: atm: Fix NULL pointer dereference
      CVE-2025-22021: netfilter: socket: Lookup orig tuple for IPv6 SNAT
      CVE-2025-22035: tracing: Fix use-after-free in print_graph_function_flags during tracer switching
      CVE-2025-22054: arcnet: Add NULL check in com20020pci_probe()
      CVE-2025-22063: netlabel: Fix NULL pointer exception caused by CALIPSO on IPv4 sockets
      CVE-2025-22071: spufs: fix a leak in spufs_create_context()
      CVE-2025-22073: spufs: fix a leak on spufs_new_file() failure
      CVE-2025-22079: ocfs2: validate l_tree_depth to avoid out-of-bounds access
      CVE-2025-22086: RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow
      CVE-2025-23136: thermal: int340x: Add NULL check for adev
      CVE-2025-38637: net_sched: skbprio: Remove overly strict queue assertions
      CVE-2025-39735: jfs: fix slab-out-of-bounds read in ea_get()

Best regards,
Ulrich Hecht


                 reply	other threads:[~2025-05-08 11:57 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=2829441.388422.1746705413499@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=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=pavel@denx.de \
    /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