All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: stable@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	patches@lists.linux.dev, Silvio Gissi <sifonsec@amazon.com>,
	David Howells <dhowells@redhat.com>,
	Hazem Mohamed Abuelfotoh <abuehaze@amazon.com>,
	linux-afs@lists.infradead.org, linux-cifs@vger.kernel.org,
	keyrings@vger.kernel.org, netdev@vger.kernel.org,
	Jarkko Sakkinen <jarkko@kernel.org>
Subject: [PATCH 6.9 4/5] keys: Fix overwrite of key expiration on instantiation
Date: Wed, 15 May 2024 10:26:41 +0200	[thread overview]
Message-ID: <20240515082346.076396212@linuxfoundation.org> (raw)
In-Reply-To: <20240515082345.213796290@linuxfoundation.org>

6.9-stable review patch.  If anyone has any objections, please let me know.

------------------

From: Silvio Gissi <sifonsec@amazon.com>

commit 9da27fb65a14c18efd4473e2e82b76b53ba60252 upstream.

The expiry time of a key is unconditionally overwritten during
instantiation, defaulting to turn it permanent. This causes a problem
for DNS resolution as the expiration set by user-space is overwritten to
TIME64_MAX, disabling further DNS updates. Fix this by restoring the
condition that key_set_expiry is only called when the pre-parser sets a
specific expiry.

Fixes: 39299bdd2546 ("keys, dns: Allow key types (eg. DNS) to be reclaimed immediately on expiry")
Signed-off-by: Silvio Gissi <sifonsec@amazon.com>
cc: David Howells <dhowells@redhat.com>
cc: Hazem Mohamed Abuelfotoh <abuehaze@amazon.com>
cc: linux-afs@lists.infradead.org
cc: linux-cifs@vger.kernel.org
cc: keyrings@vger.kernel.org
cc: netdev@vger.kernel.org
cc: stable@vger.kernel.org
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
 security/keys/key.c |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

--- a/security/keys/key.c
+++ b/security/keys/key.c
@@ -463,7 +463,8 @@ static int __key_instantiate_and_link(st
 			if (authkey)
 				key_invalidate(authkey);
 
-			key_set_expiry(key, prep->expiry);
+			if (prep->expiry != TIME64_MAX)
+				key_set_expiry(key, prep->expiry);
 		}
 	}
 



  parent reply	other threads:[~2024-05-15  8:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15  8:26 [PATCH 6.9 0/5] 6.9.1-rc1 review Greg Kroah-Hartman
2024-05-15  8:26 ` [PATCH 6.9 1/5] VFIO: Add the SPR_DSA and SPR_IAX devices to the denylist Greg Kroah-Hartman
2024-05-15  8:26 ` [PATCH 6.9 2/5] dmaengine: idxd: add a new security check to deal with a hardware erratum Greg Kroah-Hartman
2024-05-15  8:26 ` [PATCH 6.9 3/5] dmaengine: idxd: add a write() method for applications to submit work Greg Kroah-Hartman
2024-05-15  8:26 ` Greg Kroah-Hartman [this message]
2024-05-15  8:26 ` [PATCH 6.9 5/5] wifi: mt76: mt7915: add missing chanctx ops Greg Kroah-Hartman
2024-05-15 18:38 ` [PATCH 6.9 0/5] 6.9.1-rc1 review Ron Economos
2024-05-15 18:57 ` Florian Fainelli
2024-05-15 19:54 ` Shuah Khan
2024-05-16  8:40 ` Naresh Kamboju
2024-05-16 12:03 ` Mark Brown
2024-05-17  2:37 ` Bagas Sanjaya
2024-05-17  9:28 ` Jon Hunter

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=20240515082346.076396212@linuxfoundation.org \
    --to=gregkh@linuxfoundation.org \
    --cc=abuehaze@amazon.com \
    --cc=dhowells@redhat.com \
    --cc=jarkko@kernel.org \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=sifonsec@amazon.com \
    --cc=stable@vger.kernel.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.