From: Pavel Machek <pavel@nabladev.com>
To: whyshall.dev@gmail.com
Cc: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] [ANNOUNCE] Release v4.19.325-cip135
Date: Wed, 5 Aug 2026 10:46:47 +0200 [thread overview]
Message-ID: <anL4d800j3arkffa@duo.ucw.cz> (raw)
In-Reply-To: <1252941.1785911162738531742@lists.cip-project.org>
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
Hi!
>
> I understand that the CIP project addresses vulnerabilities in the Linux 4.19.325 base kernel and releases updated versions such as 4.19.325-cipX, with the latest release currently being 4.19.325-cip135.
>
> Could you please let me know:
We don't really have answers to these questions. Due to low quality of
recent CVE entries, we don't track them closely.
> How many CVEs relevant to the 4.19.325 kernel are still unresolved?
> How many of these CVEs are expected to be addressed in future CIP releases?
> Is there an estimated CIP release number (cipX) by which all relevant CVEs will have been addressed?
Best regards,
Pavel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2026-08-05 8:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 13:43 [ANNOUNCE] Release v4.19.325-cip135 Ulrich Hecht
2026-08-05 6:26 ` whyshall
2026-08-05 8:46 ` Pavel Machek [this message]
2026-08-05 20:27 ` [cip-dev] " 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=anL4d800j3arkffa@duo.ucw.cz \
--to=pavel@nabladev.com \
--cc=cip-dev@lists.cip-project.org \
--cc=whyshall.dev@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.