diff --git a/Fix-live-debugging-with-lockdown-integrity.patch b/Fix-live-debugging-with-lockdown-integrity.patch
new file mode 100644
index 0000000000000000000000000000000000000000..5e9eedd95df2c365e618e640815b4e623401baaa
--- /dev/null
+++ b/Fix-live-debugging-with-lockdown-integrity.patch
@@ -0,0 +1,57 @@
+From e90c0011d6e9476104c4c43aa76d2d0830a15946 Mon Sep 17 00:00:00 2001
+From: Philipp Rudo <prudo@redhat.com>
+Date: Tue, 9 Nov 2021 14:52:22 +0100
+Subject: [PATCH] Fix live debugging with lockdown=integrity
+
+With kernel lockdown the access to kernel interfaces that allow to
+extract confidential information (lockdown=confidentiality) or modify a
+running kernel (lockdown=integrity) can be restricted. Two of the
+interfaces that can be restricted are /dev/mem (integrity &
+confidentiality) and /proc/kcore (confidentiality). With
+lockdown=integrity this leads to a situation where /dev/mem exists but
+is not readable while /proc/kcore exists and is readable. This breaks
+crash's live debugging when it is invoked without argument, i.e.
+
+$ crash
+[...]
+crash: /dev/mem: Operation not permitted
+
+while passing /proc/kcore as image succeeds. The reason for this is that
+crash always picks /dev/mem as source when it exits but doesn't check if
+it is readable. Fix this by only selecting /dev/mem when it is readable.
+
+Signed-off-by: Philipp Rudo <prudo@redhat.com>
+---
+ filesys.c | 2 +-
+ main.c    | 2 +-
+ 2 files changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/filesys.c b/filesys.c
+index 3361b6c..43cbe82 100644
+--- a/filesys.c
++++ b/filesys.c
+@@ -3666,7 +3666,7 @@ get_live_memory_source(void)
+ 	if (pc->live_memsrc)
+ 		goto live_report;
+ 
+-	if (file_exists("/dev/mem", NULL))
++	if (file_readable("/dev/mem"))
+ 		pc->live_memsrc = "/dev/mem";
+ 	else if (file_exists("/proc/kcore", NULL)) {
+ 		pc->flags &= ~DEVMEM;
+diff --git a/main.c b/main.c
+index 388ac46..dfd343c 100644
+--- a/main.c
++++ b/main.c
+@@ -1119,7 +1119,7 @@ setup_environment(int argc, char **argv)
+ 	pc->flags2 |= REDZONE;
+ 	pc->confd = -2;
+ 	pc->machine_type = MACHINE_TYPE;
+-	if (file_exists("/dev/mem", NULL)) {     /* defaults until argv[] is parsed */
++	if (file_readable("/dev/mem")) {     /* defaults until argv[] is parsed */
+ 		pc->readmem = read_dev_mem;
+ 		pc->writemem = write_dev_mem;
+ 	} else if (file_exists("/proc/kcore", NULL)) {
+-- 
+2.27.0
+
diff --git a/crash.spec b/crash.spec
index 10253202a605276f15ca8e0b1e5dfca2c31cc1bb..4765d1ce4dae2b036d4cd77a577181e3ad531671 100644
--- a/crash.spec
+++ b/crash.spec
@@ -1,6 +1,6 @@
 Name: crash
 Version: 7.3.0
-Release: 5
+Release: 6
 Summary: Linux kernel crash utility.
 License: GPLv3
 URL: https://crash-utility.github.io
@@ -14,6 +14,7 @@ Patch4: 0003-arm64-use-dedicated-bits-to-record-the-VA-space-layo.patch
 Patch5: 0004-arm64-implement-switchable-PTOV-VTOP-for-kernels-5.1.patch
 Patch6:	add-SDEI-stack-resolution.patch
 Patch7: Handle-task_struct-cpu-member-changes-for-kernels-5..patch
+Patch8: Fix-live-debugging-with-lockdown-integrity.patch
 
 BuildRequires: ncurses-devel zlib-devel lzo-devel snappy-devel
 BuildRequires: gcc gcc-c++ bison m4
@@ -79,6 +80,10 @@ install -D -m 0644 defs.h %{buildroot}%{_includedir}/%{name}/defs.h
 %{_mandir}/man8/crash.8*
 
 %changelog
+* Tue Jun 28 2022 jiazhenyuan <jiazhenyuan@uniontech.com> - 7.3.0-6
+- fix live debugging with error "cannot determine VA_BITS_ACTUAL:
+  please use /proc/kcore"
+
 * Wed Feb 23 2022 wangbin <wangbin224@huawei.com> - 7.3.0-5
 - Handle task_struct cpu member changes for kernels >= 5.16-rc1
   and delete use_system_readline_v3.patch