All of lore.kernel.org
 help / color / mirror / Atom feed
From: "whyshall" <whyshall.dev@gmail.com>
To: cip-dev@lists.cip-project.org
Subject: Re: [ANNOUNCE] Release v4.19.325-cip135
Date: Tue, 04 Aug 2026 23:26:02 -0700	[thread overview]
Message-ID: <1252941.1785911162738531742@lists.cip-project.org> (raw)
In-Reply-To: <1672269011.888387.1785850990322@webmail.strato.de>

[-- Attachment #1: Type: text/plain, Size: 604 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:

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?
Does CIP only focus on critical vulnerabilities or it would solve all reported vulnerabilities ?

Thanks.

[-- Attachment #2: Type: text/html, Size: 659 bytes --]

  reply	other threads:[~2026-08-05  6:26 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 [this message]
2026-08-05  8:46   ` [cip-dev] " Pavel Machek
2026-08-05 20:27     ` 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=1252941.1785911162738531742@lists.cip-project.org \
    --to=whyshall.dev@gmail.com \
    --cc=cip-dev@lists.cip-project.org \
    /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.