idx int64 | project string | commit_id string | project_url string | commit_url string | commit_message string | target int64 | func string | func_hash float64 | file_name string | file_hash float64 | cwe list | cve string | cve_desc string | nvd_url string |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
159,186 | FFmpeg | e8714f6f93d1a32f4e4655209960afcf4c185214 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/e8714f6f93d1a32f4e4655209960afcf4c185214 | avcodec/h264: Clear delayed_pic on deallocation
Fixes use of freed memory
Fixes: case5_av_frame_copy_props.mp4
Found-by: Michal Zalewski <lcamtuf@coredump.cx>
Signed-off-by: Michael Niedermayer <michaelni@gmx.at> | 0 | void ff_h264_free_tables(H264Context *h, int free_rbsp)
{
int i;
H264Context *hx;
av_freep(&h->intra4x4_pred_mode);
av_freep(&h->chroma_pred_mode_table);
av_freep(&h->cbp_table);
av_freep(&h->mvd_table[0]);
av_freep(&h->mvd_table[1]);
av_freep(&h->direct_table);
av_freep(&h->non_zer... | 150,199,390,911,375,490,000,000,000,000,000,000,000 | h264.c | 113,097,433,120,688,950,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2015-3417 | Use-after-free vulnerability in the ff_h264_free_tables function in libavcodec/h264.c in FFmpeg before 2.3.6 allows remote attackers to cause a denial of service or possibly have unspecified other impact via crafted H.264 data in an MP4 file, as demonstrated by an HTML VIDEO element that references H.264 data. | https://nvd.nist.gov/vuln/detail/CVE-2015-3417 |
1,480 | linux | 8b01fc86b9f425899f8a3a8fc1c47d73c2c20543 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8b01fc86b9f425899f8a3a8fc1c47d73c2c20543 | fs: take i_mutex during prepare_binprm for set[ug]id executables
This prevents a race between chown() and execve(), where chowning a
setuid-user binary to root would momentarily make the binary setuid
root.
This patch was mostly written by Linus Torvalds.
Signed-off-by: Jann Horn <jann@thejh.net>
Signed-off-by: Linu... | 1 | int prepare_binprm(struct linux_binprm *bprm)
{
struct inode *inode = file_inode(bprm->file);
umode_t mode = inode->i_mode;
int retval;
/* clear any previous set[ug]id data from a previous binary */
bprm->cred->euid = current_euid();
bprm->cred->egid = current_egid();
if (!(bprm->file->f_path.mnt->mnt_flags... | 335,498,349,453,083,000,000,000,000,000,000,000,000 | exec.c | 9,385,387,174,828,543,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2015-3339 | Race condition in the prepare_binprm function in fs/exec.c in the Linux kernel before 3.19.6 allows local users to gain privileges by executing a setuid program at a time instant when a chown to root is in progress, and the ownership is changed but the setuid bit is not yet stripped. | https://nvd.nist.gov/vuln/detail/CVE-2015-3339 |
159,187 | linux | 8b01fc86b9f425899f8a3a8fc1c47d73c2c20543 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8b01fc86b9f425899f8a3a8fc1c47d73c2c20543 | fs: take i_mutex during prepare_binprm for set[ug]id executables
This prevents a race between chown() and execve(), where chowning a
setuid-user binary to root would momentarily make the binary setuid
root.
This patch was mostly written by Linus Torvalds.
Signed-off-by: Jann Horn <jann@thejh.net>
Signed-off-by: Linu... | 0 | int prepare_binprm(struct linux_binprm *bprm)
{
int retval;
bprm_fill_uid(bprm);
/* fill in binprm security blob */
retval = security_bprm_set_creds(bprm);
if (retval)
return retval;
bprm->cred_prepared = 1;
memset(bprm->buf, 0, BINPRM_BUF_SIZE);
return kernel_read(bprm->file, 0, bprm->buf, BINPRM_B... | 57,500,385,887,014,850,000,000,000,000,000,000,000 | exec.c | 186,853,442,526,040,300,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2015-3339 | Race condition in the prepare_binprm function in fs/exec.c in the Linux kernel before 3.19.6 allows local users to gain privileges by executing a setuid program at a time instant when a chown to root is in progress, and the ownership is changed but the setuid bit is not yet stripped. | https://nvd.nist.gov/vuln/detail/CVE-2015-3339 |
1,481 | linux | ccfe8c3f7e52ae83155cb038753f4c75b774ca8a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ccfe8c3f7e52ae83155cb038753f4c75b774ca8a | crypto: aesni - fix memory usage in GCM decryption
The kernel crypto API logic requires the caller to provide the
length of (ciphertext || authentication tag) as cryptlen for the
AEAD decryption operation. Thus, the cipher implementation must
calculate the size of the plaintext output itself and cannot simply use
cryp... | 1 | static int __driver_rfc4106_decrypt(struct aead_request *req)
{
u8 one_entry_in_sg = 0;
u8 *src, *dst, *assoc;
unsigned long tempCipherLen = 0;
__be32 counter = cpu_to_be32(1);
int retval = 0;
struct crypto_aead *tfm = crypto_aead_reqtfm(req);
struct aesni_rfc4106_gcm_ctx *ctx = aesni_rfc4106_gcm_ctx_get(tfm);
... | 235,636,219,205,578,550,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2015-3331 | The __driver_rfc4106_decrypt function in arch/x86/crypto/aesni-intel_glue.c in the Linux kernel before 3.19.3 does not properly determine the memory locations used for encrypted data, which allows context-dependent attackers to cause a denial of service (buffer overflow and system crash) or possibly execute arbitrary c... | https://nvd.nist.gov/vuln/detail/CVE-2015-3331 |
159,188 | linux | ccfe8c3f7e52ae83155cb038753f4c75b774ca8a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ccfe8c3f7e52ae83155cb038753f4c75b774ca8a | crypto: aesni - fix memory usage in GCM decryption
The kernel crypto API logic requires the caller to provide the
length of (ciphertext || authentication tag) as cryptlen for the
AEAD decryption operation. Thus, the cipher implementation must
calculate the size of the plaintext output itself and cannot simply use
cryp... | 0 | static int __driver_rfc4106_decrypt(struct aead_request *req)
{
u8 one_entry_in_sg = 0;
u8 *src, *dst, *assoc;
unsigned long tempCipherLen = 0;
__be32 counter = cpu_to_be32(1);
int retval = 0;
struct crypto_aead *tfm = crypto_aead_reqtfm(req);
struct aesni_rfc4106_gcm_ctx *ctx = aesni_rfc4106_gcm_ctx_get(tfm);
... | 284,832,249,579,860,770,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2015-3331 | The __driver_rfc4106_decrypt function in arch/x86/crypto/aesni-intel_glue.c in the Linux kernel before 3.19.3 does not properly determine the memory locations used for encrypted data, which allows context-dependent attackers to cause a denial of service (buffer overflow and system crash) or possibly execute arbitrary c... | https://nvd.nist.gov/vuln/detail/CVE-2015-3331 |
1,488 | linux | 6fd99094de2b83d1d4c8457f2c83483b2828e75a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6fd99094de2b83d1d4c8457f2c83483b2828e75a | ipv6: Don't reduce hop limit for an interface
A local route may have a lower hop_limit set than global routes do.
RFC 3756, Section 4.2.7, "Parameter Spoofing"
> 1. The attacker includes a Current Hop Limit of one or another small
> number which the attacker knows will cause legitimate packets to
> be... | 1 | static void ndisc_router_discovery(struct sk_buff *skb)
{
struct ra_msg *ra_msg = (struct ra_msg *)skb_transport_header(skb);
struct neighbour *neigh = NULL;
struct inet6_dev *in6_dev;
struct rt6_info *rt = NULL;
int lifetime;
struct ndisc_options ndopts;
int optlen;
unsigned int pref = 0;
__u8 *opt = (__u8 *... | 143,930,665,896,709,250,000,000,000,000,000,000,000 | ndisc.c | 115,440,394,696,074,500,000,000,000,000,000,000,000 | [
"CWE-17"
] | CVE-2015-2922 | The ndisc_router_discovery function in net/ipv6/ndisc.c in the Neighbor Discovery (ND) protocol implementation in the IPv6 stack in the Linux kernel before 3.19.6 allows remote attackers to reconfigure a hop-limit setting via a small hop_limit value in a Router Advertisement (RA) message. | https://nvd.nist.gov/vuln/detail/CVE-2015-2922 |
159,194 | linux | 6fd99094de2b83d1d4c8457f2c83483b2828e75a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6fd99094de2b83d1d4c8457f2c83483b2828e75a | ipv6: Don't reduce hop limit for an interface
A local route may have a lower hop_limit set than global routes do.
RFC 3756, Section 4.2.7, "Parameter Spoofing"
> 1. The attacker includes a Current Hop Limit of one or another small
> number which the attacker knows will cause legitimate packets to
> be... | 0 | static void ndisc_router_discovery(struct sk_buff *skb)
{
struct ra_msg *ra_msg = (struct ra_msg *)skb_transport_header(skb);
struct neighbour *neigh = NULL;
struct inet6_dev *in6_dev;
struct rt6_info *rt = NULL;
int lifetime;
struct ndisc_options ndopts;
int optlen;
unsigned int pref = 0;
__u8 *opt = (__u8 *... | 1,446,993,529,465,990,800,000,000,000,000,000,000 | ndisc.c | 195,047,018,190,101,720,000,000,000,000,000,000,000 | [
"CWE-17"
] | CVE-2015-2922 | The ndisc_router_discovery function in net/ipv6/ndisc.c in the Neighbor Discovery (ND) protocol implementation in the IPv6 stack in the Linux kernel before 3.19.6 allows remote attackers to reconfigure a hop-limit setting via a small hop_limit value in a Router Advertisement (RA) message. | https://nvd.nist.gov/vuln/detail/CVE-2015-2922 |
1,489 | das_watchdog | bd20bb02e75e2c0483832b52f2577253febfb690 | https://github.com/kmatheussen/das_watchdog | https://github.com/kmatheussen/das_watchdog/commit/bd20bb02e75e2c0483832b52f2577253febfb690 | Fix memory overflow if the name of an environment is larger than 500 characters. Bug found by Adam Sampson. | 1 | static char *get_pid_environ_val(pid_t pid,char *val){
char temp[500];
int i=0;
int foundit=0;
FILE *fp;
sprintf(temp,"/proc/%d/environ",pid);
fp=fopen(temp,"r");
if(fp==NULL)
return NULL;
for(;;){
temp[i]=fgetc(fp);
if(foundit==1 && (temp[i]==0 || temp[i]=='\0' || temp[... | 127,977,327,279,497,000,000,000,000,000,000,000,000 | das_watchdog.c | 25,596,189,492,826,565,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-2831 | Buffer overflow in das_watchdog 0.9.0 allows local users to execute arbitrary code with root privileges via a large string in the XAUTHORITY environment variable. | https://nvd.nist.gov/vuln/detail/CVE-2015-2831 |
159,195 | das_watchdog | bd20bb02e75e2c0483832b52f2577253febfb690 | https://github.com/kmatheussen/das_watchdog | https://github.com/kmatheussen/das_watchdog/commit/bd20bb02e75e2c0483832b52f2577253febfb690 | Fix memory overflow if the name of an environment is larger than 500 characters. Bug found by Adam Sampson. | 0 | static char *get_pid_environ_val(pid_t pid,char *val){
int temp_size = 500;
char *temp = malloc(temp_size);
int i=0;
int foundit=0;
FILE *fp;
sprintf(temp,"/proc/%d/environ",pid);
fp=fopen(temp,"r");
if(fp==NULL)
return NULL;
for(;;){
if (i >= temp_size) {
temp_size ... | 115,661,102,088,990,040,000,000,000,000,000,000,000 | das_watchdog.c | 51,822,563,435,477,410,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-2831 | Buffer overflow in das_watchdog 0.9.0 allows local users to execute arbitrary code with root privileges via a large string in the XAUTHORITY environment variable. | https://nvd.nist.gov/vuln/detail/CVE-2015-2831 |
1,490 | krb5 | 3db8dfec1ef50ddd78d6ba9503185995876a39fd | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/3db8dfec1ef50ddd78d6ba9503185995876a39fd | Fix IAKERB context export/import [CVE-2015-2698]
The patches for CVE-2015-2696 contained a regression in the newly
added IAKERB iakerb_gss_export_sec_context() function, which could
cause it to corrupt memory. Fix the regression by properly
dereferencing the context_handle pointer before casting it.
Also, the patche... | 1 | iakerb_gss_export_sec_context(OM_uint32 *minor_status,
gss_ctx_id_t *context_handle,
gss_buffer_t interprocess_token)
{
OM_uint32 maj;
iakerb_ctx_id_t ctx = (iakerb_ctx_id_t)context_handle;
/* We don't currently support exporting partially es... | 327,336,867,353,175,950,000,000,000,000,000,000,000 | iakerb.c | 282,483,658,881,223,100,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-2698 | The iakerb_gss_export_sec_context function in lib/gssapi/krb5/iakerb.c in MIT Kerberos 5 (aka krb5) 1.14 pre-release 2015-09-14 improperly accesses a certain pointer, which allows remote authenticated users to cause a denial of service (memory corruption) or possibly have unspecified other impact by interacting with an... | https://nvd.nist.gov/vuln/detail/CVE-2015-2698 |
159,196 | krb5 | 3db8dfec1ef50ddd78d6ba9503185995876a39fd | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/3db8dfec1ef50ddd78d6ba9503185995876a39fd | Fix IAKERB context export/import [CVE-2015-2698]
The patches for CVE-2015-2696 contained a regression in the newly
added IAKERB iakerb_gss_export_sec_context() function, which could
cause it to corrupt memory. Fix the regression by properly
dereferencing the context_handle pointer before casting it.
Also, the patche... | 0 | iakerb_gss_export_sec_context(OM_uint32 *minor_status,
gss_ctx_id_t *context_handle,
gss_buffer_t interprocess_token)
{
OM_uint32 maj;
iakerb_ctx_id_t ctx = (iakerb_ctx_id_t)*context_handle;
/* We don't currently support exporting partially e... | 3,278,659,956,740,170,000,000,000,000,000,000,000 | iakerb.c | 3,159,164,415,976,342,700,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-2698 | The iakerb_gss_export_sec_context function in lib/gssapi/krb5/iakerb.c in MIT Kerberos 5 (aka krb5) 1.14 pre-release 2015-09-14 improperly accesses a certain pointer, which allows remote authenticated users to cause a denial of service (memory corruption) or possibly have unspecified other impact by interacting with an... | https://nvd.nist.gov/vuln/detail/CVE-2015-2698 |
1,491 | krb5 | f0c094a1b745d91ef2f9a4eae2149aac026a5789 | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/f0c094a1b745d91ef2f9a4eae2149aac026a5789 | Fix build_principal memory bug [CVE-2015-2697]
In build_principal_va(), use k5memdup0() instead of strdup() to make a
copy of the realm, to ensure that we allocate the correct number of
bytes and do not read past the end of the input string. This bug
affects krb5_build_principal(), krb5_build_principal_va(), and
krb5... | 1 | build_principal_va(krb5_context context, krb5_principal princ,
unsigned int rlen, const char *realm, va_list ap)
{
krb5_error_code retval = 0;
char *r = NULL;
krb5_data *data = NULL;
krb5_int32 count = 0;
krb5_int32 size = 2; /* initial guess at needed space */
char *componen... | 284,043,475,302,472,930,000,000,000,000,000,000,000 | bld_princ.c | 27,830,430,857,955,170,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-2697 | The build_principal_va function in lib/krb5/krb/bld_princ.c in MIT Kerberos 5 (aka krb5) before 1.14 allows remote authenticated users to cause a denial of service (out-of-bounds read and KDC crash) via an initial '\0' character in a long realm field within a TGS request. | https://nvd.nist.gov/vuln/detail/CVE-2015-2697 |
159,197 | krb5 | f0c094a1b745d91ef2f9a4eae2149aac026a5789 | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/f0c094a1b745d91ef2f9a4eae2149aac026a5789 | Fix build_principal memory bug [CVE-2015-2697]
In build_principal_va(), use k5memdup0() instead of strdup() to make a
copy of the realm, to ensure that we allocate the correct number of
bytes and do not read past the end of the input string. This bug
affects krb5_build_principal(), krb5_build_principal_va(), and
krb5... | 0 | build_principal_va(krb5_context context, krb5_principal princ,
unsigned int rlen, const char *realm, va_list ap)
{
krb5_error_code retval = 0;
char *r = NULL;
krb5_data *data = NULL;
krb5_int32 count = 0;
krb5_int32 size = 2; /* initial guess at needed space */
char *componen... | 305,804,102,196,884,650,000,000,000,000,000,000,000 | bld_princ.c | 304,020,427,652,410,000,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-2697 | The build_principal_va function in lib/krb5/krb/bld_princ.c in MIT Kerberos 5 (aka krb5) before 1.14 allows remote authenticated users to cause a denial of service (out-of-bounds read and KDC crash) via an initial '\0' character in a long realm field within a TGS request. | https://nvd.nist.gov/vuln/detail/CVE-2015-2697 |
1,523 | krb5 | e3b5a5e5267818c97750b266df50b6a3d4649604 | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/e3b5a5e5267818c97750b266df50b6a3d4649604 | Prevent requires_preauth bypass [CVE-2015-2694]
In the OTP kdcpreauth module, don't set the TKT_FLG_PRE_AUTH bit until
the request is successfully verified. In the PKINIT kdcpreauth
module, don't respond with code 0 on empty input or an unconfigured
realm. Together these bugs could cause the KDC preauth framework to... | 1 | pkinit_server_verify_padata(krb5_context context,
krb5_data *req_pkt,
krb5_kdc_req * request,
krb5_enc_tkt_part * enc_tkt_reply,
krb5_pa_data * data,
krb5_kdcpreauth_callbacks cb,
... | 7,409,460,042,177,961,000,000,000,000,000,000,000 | pkinit_srv.c | 27,162,181,412,772,705,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2015-2694 | The kdcpreauth modules in MIT Kerberos 5 (aka krb5) 1.12.x and 1.13.x before 1.13.2 do not properly track whether a client's request has been validated, which allows remote attackers to bypass an intended preauthentication requirement by providing (1) zero bytes of data or (2) an arbitrary realm name, related to plugin... | https://nvd.nist.gov/vuln/detail/CVE-2015-2694 |
159,226 | krb5 | e3b5a5e5267818c97750b266df50b6a3d4649604 | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/e3b5a5e5267818c97750b266df50b6a3d4649604 | Prevent requires_preauth bypass [CVE-2015-2694]
In the OTP kdcpreauth module, don't set the TKT_FLG_PRE_AUTH bit until
the request is successfully verified. In the PKINIT kdcpreauth
module, don't respond with code 0 on empty input or an unconfigured
realm. Together these bugs could cause the KDC preauth framework to... | 0 | pkinit_server_verify_padata(krb5_context context,
krb5_data *req_pkt,
krb5_kdc_req * request,
krb5_enc_tkt_part * enc_tkt_reply,
krb5_pa_data * data,
krb5_kdcpreauth_callbacks cb,
... | 293,259,105,595,044,770,000,000,000,000,000,000,000 | pkinit_srv.c | 215,794,323,367,662,820,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2015-2694 | The kdcpreauth modules in MIT Kerberos 5 (aka krb5) 1.12.x and 1.13.x before 1.13.2 do not properly track whether a client's request has been validated, which allows remote attackers to bypass an intended preauthentication requirement by providing (1) zero bytes of data or (2) an arbitrary realm name, related to plugin... | https://nvd.nist.gov/vuln/detail/CVE-2015-2694 |
1,524 | linux | f84598bd7c851f8b0bf8cd0d7c3be0d73c432ff4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f84598bd7c851f8b0bf8cd0d7c3be0d73c432ff4 | x86/microcode/intel: Guard against stack overflow in the loader
mc_saved_tmp is a static array allocated on the stack, we need to make
sure mc_saved_count stays within its bounds, otherwise we're overflowing
the stack in _save_mc(). A specially crafted microcode header could lead
to a kernel crash or potentially kerne... | 1 | get_matching_model_microcode(int cpu, unsigned long start,
void *data, size_t size,
struct mc_saved_data *mc_saved_data,
unsigned long *mc_saved_in_initrd,
struct ucode_cpu_info *uci)
{
u8 *ucode_ptr = data;
unsigned int leftover = size;
enum ucode_state state = UCODE_OK;
unsigned in... | 43,839,155,311,078,540,000,000,000,000,000,000,000 | intel_early.c | 194,639,615,795,702,100,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-2666 | Stack-based buffer overflow in the get_matching_model_microcode function in arch/x86/kernel/cpu/microcode/intel_early.c in the Linux kernel before 4.0 allows context-dependent attackers to gain privileges by constructing a crafted microcode header and leveraging root privileges for write access to the initrd. | https://nvd.nist.gov/vuln/detail/CVE-2015-2666 |
159,227 | linux | f84598bd7c851f8b0bf8cd0d7c3be0d73c432ff4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f84598bd7c851f8b0bf8cd0d7c3be0d73c432ff4 | x86/microcode/intel: Guard against stack overflow in the loader
mc_saved_tmp is a static array allocated on the stack, we need to make
sure mc_saved_count stays within its bounds, otherwise we're overflowing
the stack in _save_mc(). A specially crafted microcode header could lead
to a kernel crash or potentially kerne... | 0 | get_matching_model_microcode(int cpu, unsigned long start,
void *data, size_t size,
struct mc_saved_data *mc_saved_data,
unsigned long *mc_saved_in_initrd,
struct ucode_cpu_info *uci)
{
u8 *ucode_ptr = data;
unsigned int leftover = size;
enum ucode_state state = UCODE_OK;
unsigned in... | 116,278,544,814,541,580,000,000,000,000,000,000,000 | intel_early.c | 332,264,040,351,845,600,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-2666 | Stack-based buffer overflow in the get_matching_model_microcode function in arch/x86/kernel/cpu/microcode/intel_early.c in the Linux kernel before 4.0 allows context-dependent attackers to gain privileges by constructing a crafted microcode header and leveraging root privileges for write access to the initrd. | https://nvd.nist.gov/vuln/detail/CVE-2015-2666 |
1,529 | pacemaker | 84ac07c | https://github.com/ClusterLabs/pacemaker | https://github.com/ClusterLabs/pacemaker/commit/84ac07c | Fix: acl: Do not delay evaluation of added nodes in some situations
It is not appropriate when the node has no children as it is not a
placeholder | 1 | __xml_acl_post_process(xmlNode * xml)
{
xmlNode *cIter = __xml_first_child(xml);
xml_private_t *p = xml->_private;
if(is_set(p->flags, xpf_created)) {
xmlAttr *xIter = NULL;
/* Always allow new scaffolding, ie. node with no attributes or only an 'id' */
for (xIter = crm_firs... | 62,179,770,258,691,625,000,000,000,000,000,000,000 | xml.c | 2,819,314,212,835,514,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2015-1867 | Pacemaker before 1.1.13 does not properly evaluate added nodes, which allows remote read-only users to gain privileges via an acl command. | https://nvd.nist.gov/vuln/detail/CVE-2015-1867 |
159,231 | pacemaker | 84ac07c | https://github.com/ClusterLabs/pacemaker | https://github.com/ClusterLabs/pacemaker/commit/84ac07c | Fix: acl: Do not delay evaluation of added nodes in some situations
It is not appropriate when the node has no children as it is not a
placeholder | 0 | __xml_acl_post_process(xmlNode * xml)
{
xmlNode *cIter = __xml_first_child(xml);
xml_private_t *p = xml->_private;
if(is_set(p->flags, xpf_created)) {
xmlAttr *xIter = NULL;
char *path = xml_get_path(xml);
/* Always allow new scaffolding, ie. node with no attributes or only an ... | 3,430,364,026,341,437,300,000,000,000,000,000,000 | xml.c | 24,126,458,247,511,270,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2015-1867 | Pacemaker before 1.1.13 does not properly evaluate added nodes, which allows remote read-only users to gain privileges via an acl command. | https://nvd.nist.gov/vuln/detail/CVE-2015-1867 |
1,532 | linux | f0d1bec9d58d4c038d0ac958c9af82be6eb18045 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f0d1bec9d58d4c038d0ac958c9af82be6eb18045 | new helper: copy_page_from_iter()
parallel to copy_page_to_iter(). pipe_write() switched to it (and became
->write_iter()).
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> | 1 | pipe_write(struct kiocb *iocb, const struct iovec *_iov,
unsigned long nr_segs, loff_t ppos)
{
struct file *filp = iocb->ki_filp;
struct pipe_inode_info *pipe = filp->private_data;
ssize_t ret;
int do_wakeup;
struct iovec *iov = (struct iovec *)_iov;
size_t total_len;
ssize_t chars;
total_len = iov_l... | 332,092,449,061,268,540,000,000,000,000,000,000,000 | pipe.c | 294,209,790,332,872,760,000,000,000,000,000,000,000 | [
"CWE-17"
] | CVE-2015-1805 | The (1) pipe_read and (2) pipe_write implementations in fs/pipe.c in the Linux kernel before 3.16 do not properly consider the side effects of failed __copy_to_user_inatomic and __copy_from_user_inatomic calls, which allows local users to cause a denial of service (system crash) or possibly gain privileges via a crafte... | https://nvd.nist.gov/vuln/detail/CVE-2015-1805 |
159,234 | linux | f0d1bec9d58d4c038d0ac958c9af82be6eb18045 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f0d1bec9d58d4c038d0ac958c9af82be6eb18045 | new helper: copy_page_from_iter()
parallel to copy_page_to_iter(). pipe_write() switched to it (and became
->write_iter()).
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> | 0 | pipe_write(struct kiocb *iocb, const struct iovec *_iov,
pipe_write(struct kiocb *iocb, struct iov_iter *from)
{
struct file *filp = iocb->ki_filp;
struct pipe_inode_info *pipe = filp->private_data;
ssize_t ret = 0;
int do_wakeup = 0;
size_t total_len = iov_iter_count(from);
ssize_t chars;
/* Null write s... | 227,378,528,348,247,500,000,000,000,000,000,000,000 | None | null | [
"CWE-17"
] | CVE-2015-1805 | The (1) pipe_read and (2) pipe_write implementations in fs/pipe.c in the Linux kernel before 3.16 do not properly consider the side effects of failed __copy_to_user_inatomic and __copy_from_user_inatomic calls, which allows local users to cause a denial of service (system crash) or possibly gain privileges via a crafte... | https://nvd.nist.gov/vuln/detail/CVE-2015-1805 |
1,535 | openssl | 98ece4eebfb6cd45cc8d550c6ac0022965071afc | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/98ece4eebfb6cd45cc8d550c6ac0022965071afc | Fix race condition in NewSessionTicket
If a NewSessionTicket is received by a multi-threaded client when
attempting to reuse a previous ticket then a race condition can occur
potentially leading to a double free of the ticket data.
CVE-2015-1791
This also fixes RT#3808 where a session ID is changed for a session alr... | 1 | int ssl3_get_new_session_ticket(SSL *s)
{
int ok, al, ret = 0, ticklen;
long n;
const unsigned char *p;
unsigned char *d;
n = s->method->ssl_get_message(s,
SSL3_ST_CR_SESSION_TICKET_A,
SSL3_ST_CR_SESSION_TICKET_B,
... | 136,608,154,302,472,780,000,000,000,000,000,000,000 | None | null | [
"CWE-362"
] | CVE-2015-1791 | Race condition in the ssl3_get_new_session_ticket function in ssl/s3_clnt.c in OpenSSL before 0.9.8zg, 1.0.0 before 1.0.0s, 1.0.1 before 1.0.1n, and 1.0.2 before 1.0.2b, when used for a multi-threaded client, allows remote attackers to cause a denial of service (double free and application crash) or possibly have unspe... | https://nvd.nist.gov/vuln/detail/CVE-2015-1791 |
159,236 | openssl | 98ece4eebfb6cd45cc8d550c6ac0022965071afc | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/98ece4eebfb6cd45cc8d550c6ac0022965071afc | Fix race condition in NewSessionTicket
If a NewSessionTicket is received by a multi-threaded client when
attempting to reuse a previous ticket then a race condition can occur
potentially leading to a double free of the ticket data.
CVE-2015-1791
This also fixes RT#3808 where a session ID is changed for a session alr... | 0 | int ssl3_get_new_session_ticket(SSL *s)
{
int ok, al, ret = 0, ticklen;
long n;
const unsigned char *p;
unsigned char *d;
n = s->method->ssl_get_message(s,
SSL3_ST_CR_SESSION_TICKET_A,
SSL3_ST_CR_SESSION_TICKET_B,
... | 182,299,218,880,703,750,000,000,000,000,000,000,000 | None | null | [
"CWE-362"
] | CVE-2015-1791 | Race condition in the ssl3_get_new_session_ticket function in ssl/s3_clnt.c in OpenSSL before 0.9.8zg, 1.0.0 before 1.0.0s, 1.0.1 before 1.0.1n, and 1.0.2 before 1.0.2b, when used for a multi-threaded client, allows remote attackers to cause a denial of service (double free and application crash) or possibly have unspe... | https://nvd.nist.gov/vuln/detail/CVE-2015-1791 |
1,536 | openssl | 59302b600e8d5b77ef144e447bb046fd7ab72686 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/59302b600e8d5b77ef144e447bb046fd7ab72686 | PKCS#7: Fix NULL dereference with missing EncryptedContent.
CVE-2015-1790
Reviewed-by: Rich Salz <rsalz@openssl.org> | 1 | BIO *PKCS7_dataDecode(PKCS7 *p7, EVP_PKEY *pkey, BIO *in_bio, X509 *pcert)
{
int i, j;
BIO *out = NULL, *btmp = NULL, *etmp = NULL, *bio = NULL;
X509_ALGOR *xa;
ASN1_OCTET_STRING *data_body = NULL;
const EVP_MD *evp_md;
const EVP_CIPHER *evp_cipher = NULL;
EVP_CIPHER_CTX *evp_ctx = NULL;
... | 294,269,827,177,663,870,000,000,000,000,000,000,000 | None | null | [
"CWE-703"
] | CVE-2015-1790 | The PKCS7_dataDecodefunction in crypto/pkcs7/pk7_doit.c in OpenSSL before 0.9.8zg, 1.0.0 before 1.0.0s, 1.0.1 before 1.0.1n, and 1.0.2 before 1.0.2b allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a PKCS#7 blob that uses ASN.1 encoding and lacks inner EncryptedC... | https://nvd.nist.gov/vuln/detail/CVE-2015-1790 |
159,237 | openssl | 59302b600e8d5b77ef144e447bb046fd7ab72686 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/59302b600e8d5b77ef144e447bb046fd7ab72686 | PKCS#7: Fix NULL dereference with missing EncryptedContent.
CVE-2015-1790
Reviewed-by: Rich Salz <rsalz@openssl.org> | 0 | BIO *PKCS7_dataDecode(PKCS7 *p7, EVP_PKEY *pkey, BIO *in_bio, X509 *pcert)
{
int i, j;
BIO *out = NULL, *btmp = NULL, *etmp = NULL, *bio = NULL;
X509_ALGOR *xa;
ASN1_OCTET_STRING *data_body = NULL;
const EVP_MD *evp_md;
const EVP_CIPHER *evp_cipher = NULL;
EVP_CIPHER_CTX *evp_ctx = NULL;
... | 107,713,659,329,716,620,000,000,000,000,000,000,000 | None | null | [
"CWE-703"
] | CVE-2015-1790 | The PKCS7_dataDecodefunction in crypto/pkcs7/pk7_doit.c in OpenSSL before 0.9.8zg, 1.0.0 before 1.0.0s, 1.0.1 before 1.0.1n, and 1.0.2 before 1.0.2b allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a PKCS#7 blob that uses ASN.1 encoding and lacks inner EncryptedC... | https://nvd.nist.gov/vuln/detail/CVE-2015-1790 |
1,538 | linux | 4e7c22d447bb6d7e37bfe39ff658486ae78e8d77 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4e7c22d447bb6d7e37bfe39ff658486ae78e8d77 | x86, mm/ASLR: Fix stack randomization on 64-bit systems
The issue is that the stack for processes is not properly randomized on
64 bit architectures due to an integer overflow.
The affected function is randomize_stack_top() in file
"fs/binfmt_elf.c":
static unsigned long randomize_stack_top(unsigned long stack_top... | 1 | static unsigned int stack_maxrandom_size(void)
{
unsigned int max = 0;
if ((current->flags & PF_RANDOMIZE) &&
!(current->personality & ADDR_NO_RANDOMIZE)) {
max = ((-1U) & STACK_RND_MASK) << PAGE_SHIFT;
}
return max;
}
| 221,663,256,924,278,800,000,000,000,000,000,000,000 | mmap.c | 64,657,617,513,672,540,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2015-1593 | The stack randomization feature in the Linux kernel before 3.19.1 on 64-bit platforms uses incorrect data types for the results of bitwise left-shift operations, which makes it easier for attackers to bypass the ASLR protection mechanism by predicting the address of the top of the stack, related to the randomize_stack_... | https://nvd.nist.gov/vuln/detail/CVE-2015-1593 |
159,238 | linux | 4e7c22d447bb6d7e37bfe39ff658486ae78e8d77 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4e7c22d447bb6d7e37bfe39ff658486ae78e8d77 | x86, mm/ASLR: Fix stack randomization on 64-bit systems
The issue is that the stack for processes is not properly randomized on
64 bit architectures due to an integer overflow.
The affected function is randomize_stack_top() in file
"fs/binfmt_elf.c":
static unsigned long randomize_stack_top(unsigned long stack_top... | 0 | static unsigned int stack_maxrandom_size(void)
static unsigned long stack_maxrandom_size(void)
{
unsigned long max = 0;
if ((current->flags & PF_RANDOMIZE) &&
!(current->personality & ADDR_NO_RANDOMIZE)) {
max = ((-1UL) & STACK_RND_MASK) << PAGE_SHIFT;
}
return max;
}
| 294,496,378,712,526,240,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2015-1593 | The stack randomization feature in the Linux kernel before 3.19.1 on 64-bit platforms uses incorrect data types for the results of bitwise left-shift operations, which makes it easier for attackers to bypass the ASLR protection mechanism by predicting the address of the top of the stack, related to the randomize_stack_... | https://nvd.nist.gov/vuln/detail/CVE-2015-1593 |
1,539 | linux | 4e7c22d447bb6d7e37bfe39ff658486ae78e8d77 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4e7c22d447bb6d7e37bfe39ff658486ae78e8d77 | x86, mm/ASLR: Fix stack randomization on 64-bit systems
The issue is that the stack for processes is not properly randomized on
64 bit architectures due to an integer overflow.
The affected function is randomize_stack_top() in file
"fs/binfmt_elf.c":
static unsigned long randomize_stack_top(unsigned long stack_top... | 1 | static unsigned long randomize_stack_top(unsigned long stack_top)
{
unsigned int random_variable = 0;
if ((current->flags & PF_RANDOMIZE) &&
!(current->personality & ADDR_NO_RANDOMIZE)) {
random_variable = get_random_int() & STACK_RND_MASK;
random_variable <<= PAGE_SHIFT;
}
#ifdef CONFIG_STACK_GROWSUP... | 272,678,573,193,334,060,000,000,000,000,000,000,000 | binfmt_elf.c | 233,173,923,575,517,170,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2015-1593 | The stack randomization feature in the Linux kernel before 3.19.1 on 64-bit platforms uses incorrect data types for the results of bitwise left-shift operations, which makes it easier for attackers to bypass the ASLR protection mechanism by predicting the address of the top of the stack, related to the randomize_stack_... | https://nvd.nist.gov/vuln/detail/CVE-2015-1593 |
159,239 | linux | 4e7c22d447bb6d7e37bfe39ff658486ae78e8d77 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4e7c22d447bb6d7e37bfe39ff658486ae78e8d77 | x86, mm/ASLR: Fix stack randomization on 64-bit systems
The issue is that the stack for processes is not properly randomized on
64 bit architectures due to an integer overflow.
The affected function is randomize_stack_top() in file
"fs/binfmt_elf.c":
static unsigned long randomize_stack_top(unsigned long stack_top... | 0 | static unsigned long randomize_stack_top(unsigned long stack_top)
{
unsigned long random_variable = 0;
if ((current->flags & PF_RANDOMIZE) &&
!(current->personality & ADDR_NO_RANDOMIZE)) {
random_variable = (unsigned long) get_random_int();
random_variable &= STACK_RND_MASK;
random_variable <<= PAGE_SH... | 213,406,850,729,583,180,000,000,000,000,000,000,000 | binfmt_elf.c | 59,838,524,896,547,000,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2015-1593 | The stack randomization feature in the Linux kernel before 3.19.1 on 64-bit platforms uses incorrect data types for the results of bitwise left-shift operations, which makes it easier for attackers to bypass the ASLR protection mechanism by predicting the address of the top of the stack, related to the randomize_stack_... | https://nvd.nist.gov/vuln/detail/CVE-2015-1593 |
1,542 | linux | 600ddd6825543962fb807884169e57b580dba208 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/600ddd6825543962fb807884169e57b580dba208 | net: sctp: fix slab corruption from use after free on INIT collisions
When hitting an INIT collision case during the 4WHS with AUTH enabled, as
already described in detail in commit 1be9a950c646 ("net: sctp: inherit
auth_capable on INIT collisions"), it can happen that we occasionally
still remotely trigger the follow... | 1 | void sctp_assoc_update(struct sctp_association *asoc,
struct sctp_association *new)
{
struct sctp_transport *trans;
struct list_head *pos, *temp;
/* Copy in new parameters of peer. */
asoc->c = new->c;
asoc->peer.rwnd = new->peer.rwnd;
asoc->peer.sack_needed = new->peer.sack_needed;
asoc->peer.auth_cap... | 245,205,618,481,032,000,000,000,000,000,000,000,000 | associola.c | 137,893,471,795,738,340,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2015-1421 | Use-after-free vulnerability in the sctp_assoc_update function in net/sctp/associola.c in the Linux kernel before 3.18.8 allows remote attackers to cause a denial of service (slab corruption and panic) or possibly have unspecified other impact by triggering an INIT collision that leads to improper handling of shared-ke... | https://nvd.nist.gov/vuln/detail/CVE-2015-1421 |
159,241 | linux | 600ddd6825543962fb807884169e57b580dba208 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/600ddd6825543962fb807884169e57b580dba208 | net: sctp: fix slab corruption from use after free on INIT collisions
When hitting an INIT collision case during the 4WHS with AUTH enabled, as
already described in detail in commit 1be9a950c646 ("net: sctp: inherit
auth_capable on INIT collisions"), it can happen that we occasionally
still remotely trigger the follow... | 0 | void sctp_assoc_update(struct sctp_association *asoc,
struct sctp_association *new)
{
struct sctp_transport *trans;
struct list_head *pos, *temp;
/* Copy in new parameters of peer. */
asoc->c = new->c;
asoc->peer.rwnd = new->peer.rwnd;
asoc->peer.sack_needed = new->peer.sack_needed;
asoc->peer.auth_cap... | 121,758,837,712,945,530,000,000,000,000,000,000,000 | associola.c | 168,553,778,830,504,050,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2015-1421 | Use-after-free vulnerability in the sctp_assoc_update function in net/sctp/associola.c in the Linux kernel before 3.18.8 allows remote attackers to cause a denial of service (slab corruption and panic) or possibly have unspecified other impact by triggering an INIT collision that leads to improper handling of shared-ke... | https://nvd.nist.gov/vuln/detail/CVE-2015-1421 |
1,565 | lxc | 72cf81f6a3404e35028567db2c99a90406e9c6e6 | https://github.com/lxc/lxc | https://github.com/lxc/lxc/commit/72cf81f6a3404e35028567db2c99a90406e9c6e6 | CVE-2015-1331: lxclock: use /run/lxc/lock rather than /run/lock/lxc
This prevents an unprivileged user to use LXC to create arbitrary file
on the filesystem.
Signed-off-by: Serge Hallyn <serge.hallyn@ubuntu.com>
Signed-off-by: Tyler Hicks <tyhicks@canonical.com>
Acked-by: Stéphane Graber <stgraber@ubuntu.com> | 1 | static char *lxclock_name(const char *p, const char *n)
{
int ret;
int len;
char *dest;
char *rundir;
/* lockfile will be:
* "/run" + "/lock/lxc/$lxcpath/$lxcname + '\0' if root
* or
* $XDG_RUNTIME_DIR + "/lock/lxc/$lxcpath/$lxcname + '\0' if non-root
*/
/* length of "/lock/lxc/" + $lxcpath + "/" ... | 245,452,041,723,366,300,000,000,000,000,000,000,000 | lxclock.c | 215,606,032,687,124,040,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2015-1331 | lxclock.c in LXC 1.1.2 and earlier allows local users to create arbitrary files via a symlink attack on /run/lock/lxc/*. | https://nvd.nist.gov/vuln/detail/CVE-2015-1331 |
159,260 | lxc | 72cf81f6a3404e35028567db2c99a90406e9c6e6 | https://github.com/lxc/lxc | https://github.com/lxc/lxc/commit/72cf81f6a3404e35028567db2c99a90406e9c6e6 | CVE-2015-1331: lxclock: use /run/lxc/lock rather than /run/lock/lxc
This prevents an unprivileged user to use LXC to create arbitrary file
on the filesystem.
Signed-off-by: Serge Hallyn <serge.hallyn@ubuntu.com>
Signed-off-by: Tyler Hicks <tyhicks@canonical.com>
Acked-by: Stéphane Graber <stgraber@ubuntu.com> | 0 | static char *lxclock_name(const char *p, const char *n)
{
int ret;
int len;
char *dest;
char *rundir;
/* lockfile will be:
* "/run" + "/lxc/lock/$lxcpath/$lxcname + '\0' if root
* or
* $XDG_RUNTIME_DIR + "/lxc/lock/$lxcpath/$lxcname + '\0' if non-root
*/
/* length of "/lxc/lock/" + $lxcpath + "/" ... | 176,754,954,954,050,100,000,000,000,000,000,000,000 | lxclock.c | 90,398,820,160,443,180,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2015-1331 | lxclock.c in LXC 1.1.2 and earlier allows local users to create arbitrary files via a symlink attack on /run/lock/lxc/*. | https://nvd.nist.gov/vuln/detail/CVE-2015-1331 |
1,567 | libuv | 66ab38918c911bcff025562cf06237d7fedaba0c | https://github.com/libuv/libuv | https://github.com/libuv/libuv/commit/66ab38918c911bcff025562cf06237d7fedaba0c | unix: call setgoups before calling setuid/setgid
Partial fix for #1093 | 1 | static void uv__process_child_init(const uv_process_options_t* options,
int stdio_count,
int (*pipes)[2],
int error_fd) {
int close_fd;
int use_fd;
int fd;
if (options->flags & UV_PROCESS_DETACHED)
sets... | 260,532,967,559,578,820,000,000,000,000,000,000,000 | process.c | 230,071,590,411,145,400,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2015-0278 | libuv before 0.10.34 does not properly drop group privileges, which allows context-dependent attackers to gain privileges via unspecified vectors. | https://nvd.nist.gov/vuln/detail/CVE-2015-0278 |
159,262 | libuv | 66ab38918c911bcff025562cf06237d7fedaba0c | https://github.com/libuv/libuv | https://github.com/libuv/libuv/commit/66ab38918c911bcff025562cf06237d7fedaba0c | unix: call setgoups before calling setuid/setgid
Partial fix for #1093 | 0 | static void uv__process_child_init(const uv_process_options_t* options,
int stdio_count,
int (*pipes)[2],
int error_fd) {
int close_fd;
int use_fd;
int fd;
if (options->flags & UV_PROCESS_DETACHED)
sets... | 224,716,456,293,320,400,000,000,000,000,000,000,000 | process.c | 132,015,908,217,795,290,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2015-0278 | libuv before 0.10.34 does not properly drop group privileges, which allows context-dependent attackers to gain privileges via unspecified vectors. | https://nvd.nist.gov/vuln/detail/CVE-2015-0278 |
1,578 | linux | f3747379accba8e95d70cec0eae0582c8c182050 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f3747379accba8e95d70cec0eae0582c8c182050 | KVM: x86: SYSENTER emulation is broken
SYSENTER emulation is broken in several ways:
1. It misses the case of 16-bit code segments completely (CVE-2015-0239).
2. MSR_IA32_SYSENTER_CS is checked in 64-bit mode incorrectly (bits 0 and 1 can
still be set without causing #GP).
3. MSR_IA32_SYSENTER_EIP and MSR_IA32_SYSE... | 1 | static int em_sysenter(struct x86_emulate_ctxt *ctxt)
{
const struct x86_emulate_ops *ops = ctxt->ops;
struct desc_struct cs, ss;
u64 msr_data;
u16 cs_sel, ss_sel;
u64 efer = 0;
ops->get_msr(ctxt, MSR_EFER, &efer);
/* inject #GP if in real mode */
if (ctxt->mode == X86EMUL_MODE_REAL)
return emulate_gp(ctxt, ... | 288,467,064,513,453,420,000,000,000,000,000,000,000 | emulate.c | 260,001,730,116,912,800,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2015-0239 | The em_sysenter function in arch/x86/kvm/emulate.c in the Linux kernel before 3.18.5, when the guest OS lacks SYSENTER MSR initialization, allows guest OS users to gain guest OS privileges or cause a denial of service (guest OS crash) by triggering use of a 16-bit code segment for emulation of a SYSENTER instruction. | https://nvd.nist.gov/vuln/detail/CVE-2015-0239 |
159,273 | linux | f3747379accba8e95d70cec0eae0582c8c182050 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f3747379accba8e95d70cec0eae0582c8c182050 | KVM: x86: SYSENTER emulation is broken
SYSENTER emulation is broken in several ways:
1. It misses the case of 16-bit code segments completely (CVE-2015-0239).
2. MSR_IA32_SYSENTER_CS is checked in 64-bit mode incorrectly (bits 0 and 1 can
still be set without causing #GP).
3. MSR_IA32_SYSENTER_EIP and MSR_IA32_SYSE... | 0 | static int em_sysenter(struct x86_emulate_ctxt *ctxt)
{
const struct x86_emulate_ops *ops = ctxt->ops;
struct desc_struct cs, ss;
u64 msr_data;
u16 cs_sel, ss_sel;
u64 efer = 0;
ops->get_msr(ctxt, MSR_EFER, &efer);
/* inject #GP if in real mode */
if (ctxt->mode == X86EMUL_MODE_REAL)
return emulate_gp(ctxt, ... | 84,720,843,148,772,850,000,000,000,000,000,000,000 | emulate.c | 237,765,955,197,371,130,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2015-0239 | The em_sysenter function in arch/x86/kvm/emulate.c in the Linux kernel before 3.18.5, when the guest OS lacks SYSENTER MSR initialization, allows guest OS users to gain guest OS privileges or cause a denial of service (guest OS crash) by triggering use of a 16-bit code segment for emulation of a SYSENTER instruction. | https://nvd.nist.gov/vuln/detail/CVE-2015-0239 |
1,579 | php-src | b585a3aed7880a5fa5c18e2b838fc96f40e075bd | https://github.com/php/php-src | https://github.com/php/php-src/commit/b585a3aed7880a5fa5c18e2b838fc96f40e075bd | Fix for bug #68710 (Use After Free Vulnerability in PHP's unserialize()) | 1 | static inline int process_nested_data(UNSERIALIZE_PARAMETER, HashTable *ht, long elements, int objprops)
{
while (elements-- > 0) {
zval *key, *data, **old_data;
ALLOC_INIT_ZVAL(key);
if (!php_var_unserialize(&key, p, max, NULL TSRMLS_CC)) {
zval_dtor(key);
FREE_ZVAL(key);
return 0;
}
if (Z_TYPE_... | 722,330,690,057,935,600,000,000,000,000,000,000 | None | null | [
"CWE-94"
] | CVE-2015-0231 | Use-after-free vulnerability in the process_nested_data function in ext/standard/var_unserializer.re in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5 allows remote attackers to execute arbitrary code via a crafted unserialize call that leverages improper handling of duplicate numerical keys within the ... | https://nvd.nist.gov/vuln/detail/CVE-2015-0231 |
159,274 | php-src | b585a3aed7880a5fa5c18e2b838fc96f40e075bd | https://github.com/php/php-src | https://github.com/php/php-src/commit/b585a3aed7880a5fa5c18e2b838fc96f40e075bd | Fix for bug #68710 (Use After Free Vulnerability in PHP's unserialize()) | 0 | static inline int process_nested_data(UNSERIALIZE_PARAMETER, HashTable *ht, long elements, int objprops)
{
while (elements-- > 0) {
zval *key, *data, **old_data;
ALLOC_INIT_ZVAL(key);
if (!php_var_unserialize(&key, p, max, NULL TSRMLS_CC)) {
zval_dtor(key);
FREE_ZVAL(key);
return 0;
}
if (Z_TYPE_... | 208,690,365,661,200,300,000,000,000,000,000,000,000 | None | null | [
"CWE-94"
] | CVE-2015-0231 | Use-after-free vulnerability in the process_nested_data function in ext/standard/var_unserializer.re in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5 allows remote attackers to execute arbitrary code via a crafted unserialize call that leverages improper handling of duplicate numerical keys within the ... | https://nvd.nist.gov/vuln/detail/CVE-2015-0231 |
1,580 | openssl | 103b171d8fc282ef435f8de9afbf7782e312961f | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/103b171d8fc282ef435f8de9afbf7782e312961f | A memory leak can occur in dtls1_buffer_record if either of the calls to
ssl3_setup_buffers or pqueue_insert fail. The former will fail if there is a
malloc failure, whilst the latter will fail if attempting to add a duplicate
record to the queue. This should never happen because duplicate records should
be detected an... | 1 | dtls1_buffer_record(SSL *s, record_pqueue *queue, unsigned char *priority)
{
DTLS1_RECORD_DATA *rdata;
pitem *item;
/* Limit the size of the queue to prevent DOS attacks */
if (pqueue_size(queue->q) >= 100)
return 0;
rdata = OPENSSL_malloc(sizeof(DTLS1_RECORD_DATA));
item = pitem_new(priority, rdata);
... | 114,939,372,772,634,080,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2015-0206 | Memory leak in the dtls1_buffer_record function in d1_pkt.c in OpenSSL 1.0.0 before 1.0.0p and 1.0.1 before 1.0.1k allows remote attackers to cause a denial of service (memory consumption) by sending many duplicate records for the next epoch, leading to failure of replay detection. | https://nvd.nist.gov/vuln/detail/CVE-2015-0206 |
159,275 | openssl | 103b171d8fc282ef435f8de9afbf7782e312961f | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/103b171d8fc282ef435f8de9afbf7782e312961f | A memory leak can occur in dtls1_buffer_record if either of the calls to
ssl3_setup_buffers or pqueue_insert fail. The former will fail if there is a
malloc failure, whilst the latter will fail if attempting to add a duplicate
record to the queue. This should never happen because duplicate records should
be detected an... | 0 | dtls1_buffer_record(SSL *s, record_pqueue *queue, unsigned char *priority)
{
DTLS1_RECORD_DATA *rdata;
pitem *item;
/* Limit the size of the queue to prevent DOS attacks */
if (pqueue_size(queue->q) >= 100)
return 0;
rdata = OPENSSL_malloc(sizeof(DTLS1_RECORD_DATA));
item = pitem_new(priority, rdata);
... | 60,176,751,094,987,280,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2015-0206 | Memory leak in the dtls1_buffer_record function in d1_pkt.c in OpenSSL 1.0.0 before 1.0.0p and 1.0.1 before 1.0.1k allows remote attackers to cause a denial of service (memory consumption) by sending many duplicate records for the next epoch, leading to failure of replay detection. | https://nvd.nist.gov/vuln/detail/CVE-2015-0206 |
1,584 | openssl | 1421e0c584ae9120ca1b88098f13d6d2e90b83a3 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/1421e0c584ae9120ca1b88098f13d6d2e90b83a3 | Unauthenticated DH client certificate fix.
Fix to prevent use of DH client certificates without sending
certificate verify message.
If we've used a client certificate to generate the premaster secret
ssl3_get_client_key_exchange returns 2 and ssl3_get_cert_verify is
never called.
We can only skip the certificate ver... | 1 | int ssl3_get_cert_verify(SSL *s)
{
EVP_PKEY *pkey=NULL;
unsigned char *p;
int al,ok,ret=0;
long n;
int type=0,i,j;
X509 *peer;
const EVP_MD *md = NULL;
EVP_MD_CTX mctx;
EVP_MD_CTX_init(&mctx);
n=s->method->ssl_get_message(s,
SSL3_ST_SR_CERT_VRFY_A,
SSL3_ST_SR_CERT_VRFY_B,
-1,
SSL3_RT_MAX_PLAIN_LENGT... | 212,984,391,365,092,660,000,000,000,000,000,000,000 | None | null | [
"CWE-310"
] | CVE-2015-0205 | The ssl3_get_cert_verify function in s3_srvr.c in OpenSSL 1.0.0 before 1.0.0p and 1.0.1 before 1.0.1k accepts client authentication with a Diffie-Hellman (DH) certificate without requiring a CertificateVerify message, which allows remote attackers to obtain access without knowledge of a private key via crafted TLS Hand... | https://nvd.nist.gov/vuln/detail/CVE-2015-0205 |
159,279 | openssl | 1421e0c584ae9120ca1b88098f13d6d2e90b83a3 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/1421e0c584ae9120ca1b88098f13d6d2e90b83a3 | Unauthenticated DH client certificate fix.
Fix to prevent use of DH client certificates without sending
certificate verify message.
If we've used a client certificate to generate the premaster secret
ssl3_get_client_key_exchange returns 2 and ssl3_get_cert_verify is
never called.
We can only skip the certificate ver... | 0 | int ssl3_get_cert_verify(SSL *s)
{
EVP_PKEY *pkey=NULL;
unsigned char *p;
int al,ok,ret=0;
long n;
int type=0,i,j;
X509 *peer;
const EVP_MD *md = NULL;
EVP_MD_CTX mctx;
EVP_MD_CTX_init(&mctx);
n=s->method->ssl_get_message(s,
SSL3_ST_SR_CERT_VRFY_A,
SSL3_ST_SR_CERT_VRFY_B,
-1,
SSL3_RT_MAX_PLAIN_LENGT... | 172,892,208,371,280,950,000,000,000,000,000,000,000 | None | null | [
"CWE-310"
] | CVE-2015-0205 | The ssl3_get_cert_verify function in s3_srvr.c in OpenSSL 1.0.0 before 1.0.0p and 1.0.1 before 1.0.1k accepts client authentication with a Diffie-Hellman (DH) certificate without requiring a CertificateVerify message, which allows remote attackers to obtain access without knowledge of a private key via crafted TLS Hand... | https://nvd.nist.gov/vuln/detail/CVE-2015-0205 |
1,586 | openssl | ce325c60c74b0fa784f5872404b722e120e5cab0 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/ce325c60c74b0fa784f5872404b722e120e5cab0 | Only allow ephemeral RSA keys in export ciphersuites.
OpenSSL clients would tolerate temporary RSA keys in non-export
ciphersuites. It also had an option SSL_OP_EPHEMERAL_RSA which
enabled this server side. Remove both options as they are a
protocol violation.
Thanks to Karthikeyan Bhargavan for reporting this issue.... | 1 | int ssl3_get_key_exchange(SSL *s)
{
#ifndef OPENSSL_NO_RSA
unsigned char *q,md_buf[EVP_MAX_MD_SIZE*2];
#endif
EVP_MD_CTX md_ctx;
unsigned char *param,*p;
int al,j,ok;
long i,param_len,n,alg_k,alg_a;
EVP_PKEY *pkey=NULL;
const EVP_MD *md = NULL;
#ifndef OPENSSL_NO_RSA
RSA *rsa=NULL;
#endif
#ifndef OPENSSL_NO_DH... | 19,329,931,296,243,780,000,000,000,000,000,000,000 | None | null | [
"CWE-310"
] | CVE-2015-0204 | The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k allows remote SSL servers to conduct RSA-to-EXPORT_RSA downgrade attacks and facilitate brute-force decryption by offering a weak ephemeral RSA key in a noncompliant role, related to the "FREAK" issue... | https://nvd.nist.gov/vuln/detail/CVE-2015-0204 |
159,281 | openssl | ce325c60c74b0fa784f5872404b722e120e5cab0 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/ce325c60c74b0fa784f5872404b722e120e5cab0 | Only allow ephemeral RSA keys in export ciphersuites.
OpenSSL clients would tolerate temporary RSA keys in non-export
ciphersuites. It also had an option SSL_OP_EPHEMERAL_RSA which
enabled this server side. Remove both options as they are a
protocol violation.
Thanks to Karthikeyan Bhargavan for reporting this issue.... | 0 | int ssl3_get_key_exchange(SSL *s)
{
#ifndef OPENSSL_NO_RSA
unsigned char *q,md_buf[EVP_MAX_MD_SIZE*2];
#endif
EVP_MD_CTX md_ctx;
unsigned char *param,*p;
int al,j,ok;
long i,param_len,n,alg_k,alg_a;
EVP_PKEY *pkey=NULL;
const EVP_MD *md = NULL;
#ifndef OPENSSL_NO_RSA
RSA *rsa=NULL;
#endif
#ifndef OPENSSL_NO_DH... | 21,006,237,877,289,390,000,000,000,000,000,000,000 | None | null | [
"CWE-310"
] | CVE-2015-0204 | The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k allows remote SSL servers to conduct RSA-to-EXPORT_RSA downgrade attacks and facilitate brute-force decryption by offering a weak ephemeral RSA key in a noncompliant role, related to the "FREAK" issue... | https://nvd.nist.gov/vuln/detail/CVE-2015-0204 |
1,593 | linux | e237ec37ec154564f8690c5bd1795339955eeef9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e237ec37ec154564f8690c5bd1795339955eeef9 | udf: Check component length before reading it
Check that length specified in a component of a symlink fits in the
input buffer we are reading. Also properly ignore component length for
component types that do not use it. Otherwise we read memory after end
of buffer for corrupted udf image.
Reported-by: Carl Henrik Lu... | 1 | static int udf_pc_to_char(struct super_block *sb, unsigned char *from,
int fromlen, unsigned char *to, int tolen)
{
struct pathComponent *pc;
int elen = 0;
int comp_len;
unsigned char *p = to;
/* Reserve one byte for terminating \0 */
tolen--;
while (elen < fromlen) {
pc = (struct pathComponent *)(fro... | 325,864,361,331,960,330,000,000,000,000,000,000,000 | symlink.c | 76,715,452,543,384,660,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2014-9730 | The udf_pc_to_char function in fs/udf/symlink.c in the Linux kernel before 3.18.2 relies on component lengths that are unused, which allows local users to cause a denial of service (system crash) via a crafted UDF filesystem image. | https://nvd.nist.gov/vuln/detail/CVE-2014-9730 |
159,287 | linux | e237ec37ec154564f8690c5bd1795339955eeef9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e237ec37ec154564f8690c5bd1795339955eeef9 | udf: Check component length before reading it
Check that length specified in a component of a symlink fits in the
input buffer we are reading. Also properly ignore component length for
component types that do not use it. Otherwise we read memory after end
of buffer for corrupted udf image.
Reported-by: Carl Henrik Lu... | 0 | static int udf_pc_to_char(struct super_block *sb, unsigned char *from,
int fromlen, unsigned char *to, int tolen)
{
struct pathComponent *pc;
int elen = 0;
int comp_len;
unsigned char *p = to;
/* Reserve one byte for terminating \0 */
tolen--;
while (elen < fromlen) {
pc = (struct pathComponent *)(fro... | 13,265,706,240,428,603,000,000,000,000,000,000,000 | symlink.c | 63,099,953,932,298,350,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2014-9730 | The udf_pc_to_char function in fs/udf/symlink.c in the Linux kernel before 3.18.2 relies on component lengths that are unused, which allows local users to cause a denial of service (system crash) via a crafted UDF filesystem image. | https://nvd.nist.gov/vuln/detail/CVE-2014-9730 |
1,596 | linux | 942080643bce061c3dd9d5718d3b745dcb39a8bc | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/942080643bce061c3dd9d5718d3b745dcb39a8bc | eCryptfs: Remove buggy and unnecessary write in file name decode routine
Dmitry Chernenkov used KASAN to discover that eCryptfs writes past the
end of the allocated buffer during encrypted filename decoding. This
fix corrects the issue by getting rid of the unnecessary 0 write when
the current bit offset is 2.
Signed... | 1 | ecryptfs_decode_from_filename(unsigned char *dst, size_t *dst_size,
const unsigned char *src, size_t src_size)
{
u8 current_bit_offset = 0;
size_t src_byte_offset = 0;
size_t dst_byte_offset = 0;
if (dst == NULL) {
(*dst_size) = ecryptfs_max_decoded_size(src_size);
goto out;
}
while (src_byte_offset... | 288,062,041,952,122,140,000,000,000,000,000,000,000 | crypto.c | 83,043,817,776,762,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-9683 | Off-by-one error in the ecryptfs_decode_from_filename function in fs/ecryptfs/crypto.c in the eCryptfs subsystem in the Linux kernel before 3.18.2 allows local users to cause a denial of service (buffer overflow and system crash) or possibly gain privileges via a crafted filename. | https://nvd.nist.gov/vuln/detail/CVE-2014-9683 |
159,290 | linux | 942080643bce061c3dd9d5718d3b745dcb39a8bc | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/942080643bce061c3dd9d5718d3b745dcb39a8bc | eCryptfs: Remove buggy and unnecessary write in file name decode routine
Dmitry Chernenkov used KASAN to discover that eCryptfs writes past the
end of the allocated buffer during encrypted filename decoding. This
fix corrects the issue by getting rid of the unnecessary 0 write when
the current bit offset is 2.
Signed... | 0 | ecryptfs_decode_from_filename(unsigned char *dst, size_t *dst_size,
const unsigned char *src, size_t src_size)
{
u8 current_bit_offset = 0;
size_t src_byte_offset = 0;
size_t dst_byte_offset = 0;
if (dst == NULL) {
(*dst_size) = ecryptfs_max_decoded_size(src_size);
goto out;
}
while (src_byte_offset... | 236,694,491,287,239,400,000,000,000,000,000,000,000 | crypto.c | 84,355,224,477,241,940,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-9683 | Off-by-one error in the ecryptfs_decode_from_filename function in fs/ecryptfs/crypto.c in the eCryptfs subsystem in the Linux kernel before 3.18.2 allows local users to cause a denial of service (buffer overflow and system crash) or possibly gain privileges via a crafted filename. | https://nvd.nist.gov/vuln/detail/CVE-2014-9683 |
1,600 | linux | 4943ba16bbc2db05115707b3ff7b4874e9e3c560 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4943ba16bbc2db05115707b3ff7b4874e9e3c560 | crypto: include crypto- module prefix in template
This adds the module loading prefix "crypto-" to the template lookup
as well.
For example, attempting to load 'vfat(blowfish)' via AF_ALG now correctly
includes the "crypto-" prefix at every level, correctly rejecting "vfat":
net-pf-38
algif-hash
crypto-vfat(blowf... | 1 | struct crypto_template *crypto_lookup_template(const char *name)
{
return try_then_request_module(__crypto_lookup_template(name), "%s",
name);
}
| 116,020,862,207,451,470,000,000,000,000,000,000,000 | algapi.c | 187,872,088,690,328,180,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-9644 | The Crypto API in the Linux kernel before 3.18.5 allows local users to load arbitrary kernel modules via a bind system call for an AF_ALG socket with a parenthesized module template expression in the salg_name field, as demonstrated by the vfat(aes) expression, a different vulnerability than CVE-2013-7421. | https://nvd.nist.gov/vuln/detail/CVE-2014-9644 |
159,291 | linux | 4943ba16bbc2db05115707b3ff7b4874e9e3c560 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/4943ba16bbc2db05115707b3ff7b4874e9e3c560 | crypto: include crypto- module prefix in template
This adds the module loading prefix "crypto-" to the template lookup
as well.
For example, attempting to load 'vfat(blowfish)' via AF_ALG now correctly
includes the "crypto-" prefix at every level, correctly rejecting "vfat":
net-pf-38
algif-hash
crypto-vfat(blowf... | 0 | struct crypto_template *crypto_lookup_template(const char *name)
{
return try_then_request_module(__crypto_lookup_template(name),
"crypto-%s", name);
}
| 107,877,713,376,855,160,000,000,000,000,000,000,000 | algapi.c | 144,052,797,779,895,220,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-9644 | The Crypto API in the Linux kernel before 3.18.5 allows local users to load arbitrary kernel modules via a bind system call for an AF_ALG socket with a parenthesized module template expression in the salg_name field, as demonstrated by the vfat(aes) expression, a different vulnerability than CVE-2013-7421. | https://nvd.nist.gov/vuln/detail/CVE-2014-9644 |
1,601 | file | 65437cee25199dbd385fb35901bc0011e164276c | https://github.com/file/file | https://github.com/file/file/commit/65437cee25199dbd385fb35901bc0011e164276c | Limit string printing to 100 chars, and add flags I forgot in the previous
commit. | 1 | donote(struct magic_set *ms, void *vbuf, size_t offset, size_t size,
int clazz, int swap, size_t align, int *flags, uint16_t *notecount)
{
Elf32_Nhdr nh32;
Elf64_Nhdr nh64;
size_t noff, doff;
uint32_t namesz, descsz;
unsigned char *nbuf = CAST(unsigned char *, vbuf);
if (*notecount == 0)
return 0;
--*note... | 206,842,038,504,383,380,000,000,000,000,000,000,000 | readelf.c | 196,087,564,373,822,200,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-9621 | The ELF parser in file 5.16 through 5.21 allows remote attackers to cause a denial of service via a long string. | https://nvd.nist.gov/vuln/detail/CVE-2014-9621 |
159,292 | file | 65437cee25199dbd385fb35901bc0011e164276c | https://github.com/file/file | https://github.com/file/file/commit/65437cee25199dbd385fb35901bc0011e164276c | Limit string printing to 100 chars, and add flags I forgot in the previous
commit. | 0 | donote(struct magic_set *ms, void *vbuf, size_t offset, size_t size,
int clazz, int swap, size_t align, int *flags, uint16_t *notecount)
{
Elf32_Nhdr nh32;
Elf64_Nhdr nh64;
size_t noff, doff;
uint32_t namesz, descsz;
unsigned char *nbuf = CAST(unsigned char *, vbuf);
if (*notecount == 0)
return 0;
--*note... | 254,196,863,170,058,200,000,000,000,000,000,000,000 | readelf.c | 235,900,810,204,449,600,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-9621 | The ELF parser in file 5.16 through 5.21 allows remote attackers to cause a denial of service via a long string. | https://nvd.nist.gov/vuln/detail/CVE-2014-9621 |
1,612 | linux | a3a8784454692dd72e5d5d34dcdab17b4420e74c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a3a8784454692dd72e5d5d34dcdab17b4420e74c | KEYS: close race between key lookup and freeing
When a key is being garbage collected, it's key->user would get put before
the ->destroy() callback is called, where the key is removed from it's
respective tracking structures.
This leaves a key hanging in a semi-invalid state which leaves a window open
for a different... | 1 | static noinline void key_gc_unused_keys(struct list_head *keys)
{
while (!list_empty(keys)) {
struct key *key =
list_entry(keys->next, struct key, graveyard_link);
list_del(&key->graveyard_link);
kdebug("- %u", key->serial);
key_check(key);
security_key_free(key);
/* deal with the user's key tracking... | 146,841,926,446,616,660,000,000,000,000,000,000,000 | None | null | [
"CWE-362"
] | CVE-2014-9529 | Race condition in the key_gc_unused_keys function in security/keys/gc.c in the Linux kernel through 3.18.2 allows local users to cause a denial of service (memory corruption or panic) or possibly have unspecified other impact via keyctl commands that trigger access to a key structure member during garbage collection of... | https://nvd.nist.gov/vuln/detail/CVE-2014-9529 |
159,298 | linux | a3a8784454692dd72e5d5d34dcdab17b4420e74c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a3a8784454692dd72e5d5d34dcdab17b4420e74c | KEYS: close race between key lookup and freeing
When a key is being garbage collected, it's key->user would get put before
the ->destroy() callback is called, where the key is removed from it's
respective tracking structures.
This leaves a key hanging in a semi-invalid state which leaves a window open
for a different... | 0 | static noinline void key_gc_unused_keys(struct list_head *keys)
{
while (!list_empty(keys)) {
struct key *key =
list_entry(keys->next, struct key, graveyard_link);
list_del(&key->graveyard_link);
kdebug("- %u", key->serial);
key_check(key);
security_key_free(key);
/* deal with the user's key tracking... | 247,633,680,114,411,080,000,000,000,000,000,000,000 | None | null | [
"CWE-362"
] | CVE-2014-9529 | Race condition in the key_gc_unused_keys function in security/keys/gc.c in the Linux kernel through 3.18.2 allows local users to cause a denial of service (memory corruption or panic) or possibly have unspecified other impact via keyctl commands that trigger access to a key structure member during garbage collection of... | https://nvd.nist.gov/vuln/detail/CVE-2014-9529 |
1,613 | libsndfile | dbe14f00030af5d3577f4cabbf9861db59e9c378 | https://github.com/erikd/libsndfile | https://github.com/erikd/libsndfile/commit/dbe14f00030af5d3577f4cabbf9861db59e9c378 | src/sd2.c : Fix two potential buffer read overflows.
Closes: https://github.com/erikd/libsndfile/issues/93 | 1 | sd2_parse_rsrc_fork (SF_PRIVATE *psf)
{ SD2_RSRC rsrc ;
int k, marker, error = 0 ;
psf_use_rsrc (psf, SF_TRUE) ;
memset (&rsrc, 0, sizeof (rsrc)) ;
rsrc.rsrc_len = psf_get_filelen (psf) ;
psf_log_printf (psf, "Resource length : %d (0x%04X)\n", rsrc.rsrc_len, rsrc.rsrc_len) ;
if (rsrc.rsrc_len > SIGNED_SIZEOF ... | 340,051,541,888,924,920,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-9496 | The sd2_parse_rsrc_fork function in sd2.c in libsndfile allows attackers to have unspecified impact via vectors related to a (1) map offset or (2) rsrc marker, which triggers an out-of-bounds read. | https://nvd.nist.gov/vuln/detail/CVE-2014-9496 |
159,299 | libsndfile | dbe14f00030af5d3577f4cabbf9861db59e9c378 | https://github.com/erikd/libsndfile | https://github.com/erikd/libsndfile/commit/dbe14f00030af5d3577f4cabbf9861db59e9c378 | src/sd2.c : Fix two potential buffer read overflows.
Closes: https://github.com/erikd/libsndfile/issues/93 | 0 | sd2_parse_rsrc_fork (SF_PRIVATE *psf)
{ SD2_RSRC rsrc ;
int k, marker, error = 0 ;
psf_use_rsrc (psf, SF_TRUE) ;
memset (&rsrc, 0, sizeof (rsrc)) ;
rsrc.rsrc_len = psf_get_filelen (psf) ;
psf_log_printf (psf, "Resource length : %d (0x%04X)\n", rsrc.rsrc_len, rsrc.rsrc_len) ;
if (rsrc.rsrc_len > SIGNED_SIZEOF ... | 55,208,231,588,152,110,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-9496 | The sd2_parse_rsrc_fork function in sd2.c in libsndfile allows attackers to have unspecified impact via vectors related to a (1) map offset or (2) rsrc marker, which triggers an out-of-bounds read. | https://nvd.nist.gov/vuln/detail/CVE-2014-9496 |
1,618 | krb5 | a197e92349a4aa2141b5dff12e9dd44c2a2166e3 | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/a197e92349a4aa2141b5dff12e9dd44c2a2166e3 | Fix kadm5/gssrpc XDR double free [CVE-2014-9421]
[MITKRB5-SA-2015-001] In auth_gssapi_unwrap_data(), do not free
partial deserialization results upon failure to deserialize. This
responsibility belongs to the callers, svctcp_getargs() and
svcudp_getargs(); doing it in the unwrap function results in freeing
the result... | 1 | bool_t auth_gssapi_unwrap_data(
OM_uint32 *major,
OM_uint32 *minor,
gss_ctx_id_t context,
uint32_t seq_num,
XDR *in_xdrs,
bool_t (*xdr_func)(),
caddr_t xdr_ptr)
{
gss_buffer_desc in_buf, out_buf;
XDR temp_xdrs;
uint32_t verf_seq_num;
int conf, qop;
unsigned in... | 6,731,538,295,626,295,000,000,000,000,000,000,000 | auth_gssapi_misc.c | 249,867,039,175,423,800,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2014-9421 | The auth_gssapi_unwrap_data function in lib/rpc/auth_gssapi_misc.c in MIT Kerberos 5 (aka krb5) through 1.11.5, 1.12.x through 1.12.2, and 1.13.x before 1.13.1 does not properly handle partial XDR deserialization, which allows remote authenticated users to cause a denial of service (use-after-free and double free, and ... | https://nvd.nist.gov/vuln/detail/CVE-2014-9421 |
159,303 | krb5 | a197e92349a4aa2141b5dff12e9dd44c2a2166e3 | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/a197e92349a4aa2141b5dff12e9dd44c2a2166e3 | Fix kadm5/gssrpc XDR double free [CVE-2014-9421]
[MITKRB5-SA-2015-001] In auth_gssapi_unwrap_data(), do not free
partial deserialization results upon failure to deserialize. This
responsibility belongs to the callers, svctcp_getargs() and
svcudp_getargs(); doing it in the unwrap function results in freeing
the result... | 0 | bool_t auth_gssapi_unwrap_data(
OM_uint32 *major,
OM_uint32 *minor,
gss_ctx_id_t context,
uint32_t seq_num,
XDR *in_xdrs,
bool_t (*xdr_func)(),
caddr_t xdr_ptr)
{
gss_buffer_desc in_buf, out_buf;
XDR temp_xdrs;
uint32_t verf_seq_num;
int conf, qop;
unsigned in... | 81,035,704,784,600,220,000,000,000,000,000,000,000 | auth_gssapi_misc.c | 174,418,160,332,606,370,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2014-9421 | The auth_gssapi_unwrap_data function in lib/rpc/auth_gssapi_misc.c in MIT Kerberos 5 (aka krb5) through 1.11.5, 1.12.x through 1.12.2, and 1.13.x before 1.13.1 does not properly handle partial XDR deserialization, which allows remote authenticated users to cause a denial of service (use-after-free and double free, and ... | https://nvd.nist.gov/vuln/detail/CVE-2014-9421 |
1,619 | openssl | 470990fee0182566d439ef7e82d1abf18b7085d7 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/470990fee0182566d439ef7e82d1abf18b7085d7 | Free up s->d1->buffered_app_data.q properly.
PR#3286 | 1 | static void dtls1_clear_queues(SSL *s)
{
pitem *item = NULL;
hm_fragment *frag = NULL;
DTLS1_RECORD_DATA *rdata;
while( (item = pqueue_pop(s->d1->unprocessed_rcds.q)) != NULL)
{
rdata = (DTLS1_RECORD_DATA *) item->data;
if (rdata->rbuf.buf)
{
OPENSSL_free(rdata->rbuf.buf);
}
... | 120,961,465,274,779,570,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-8176 | The dtls1_clear_queues function in ssl/d1_lib.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h frees data structures without considering that application data can arrive between a ChangeCipherSpec message and a Finished message, which allows remote DTLS peers to cause a denial of service (memor... | https://nvd.nist.gov/vuln/detail/CVE-2014-8176 |
159,304 | openssl | 470990fee0182566d439ef7e82d1abf18b7085d7 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/470990fee0182566d439ef7e82d1abf18b7085d7 | Free up s->d1->buffered_app_data.q properly.
PR#3286 | 0 | static void dtls1_clear_queues(SSL *s)
{
pitem *item = NULL;
hm_fragment *frag = NULL;
DTLS1_RECORD_DATA *rdata;
while( (item = pqueue_pop(s->d1->unprocessed_rcds.q)) != NULL)
{
rdata = (DTLS1_RECORD_DATA *) item->data;
if (rdata->rbuf.buf)
{
OPENSSL_free(rdata->rbuf.buf);
}
... | 123,275,068,212,067,630,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2014-8176 | The dtls1_clear_queues function in ssl/d1_lib.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h frees data structures without considering that application data can arrive between a ChangeCipherSpec message and a Finished message, which allows remote DTLS peers to cause a denial of service (memor... | https://nvd.nist.gov/vuln/detail/CVE-2014-8176 |
1,634 | linux | db29a9508a9246e77087c5531e45b2c88ec6988b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/db29a9508a9246e77087c5531e45b2c88ec6988b | netfilter: conntrack: disable generic tracking for known protocols
Given following iptables ruleset:
-P FORWARD DROP
-A FORWARD -m sctp --dport 9 -j ACCEPT
-A FORWARD -p tcp --dport 80 -j ACCEPT
-A FORWARD -p tcp -m conntrack -m state ESTABLISHED,RELATED -j ACCEPT
One would assume that this allows SCTP on port 9 and... | 1 | static bool generic_new(struct nf_conn *ct, const struct sk_buff *skb,
unsigned int dataoff, unsigned int *timeouts)
{
return true;
}
| 94,206,534,282,979,970,000,000,000,000,000,000,000 | nf_conntrack_proto_generic.c | 39,813,758,207,073,290,000,000,000,000,000,000,000 | [
"CWE-254"
] | CVE-2014-8160 | net/netfilter/nf_conntrack_proto_generic.c in the Linux kernel before 3.18 generates incorrect conntrack entries during handling of certain iptables rule sets for the SCTP, DCCP, GRE, and UDP-Lite protocols, which allows remote attackers to bypass intended access restrictions via packets with disallowed port numbers. | https://nvd.nist.gov/vuln/detail/CVE-2014-8160 |
159,319 | linux | db29a9508a9246e77087c5531e45b2c88ec6988b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/db29a9508a9246e77087c5531e45b2c88ec6988b | netfilter: conntrack: disable generic tracking for known protocols
Given following iptables ruleset:
-P FORWARD DROP
-A FORWARD -m sctp --dport 9 -j ACCEPT
-A FORWARD -p tcp --dport 80 -j ACCEPT
-A FORWARD -p tcp -m conntrack -m state ESTABLISHED,RELATED -j ACCEPT
One would assume that this allows SCTP on port 9 and... | 0 | static bool generic_new(struct nf_conn *ct, const struct sk_buff *skb,
unsigned int dataoff, unsigned int *timeouts)
{
return nf_generic_should_process(nf_ct_protonum(ct));
}
| 193,169,942,948,406,480,000,000,000,000,000,000,000 | nf_conntrack_proto_generic.c | 35,886,450,322,559,570,000,000,000,000,000,000,000 | [
"CWE-254"
] | CVE-2014-8160 | net/netfilter/nf_conntrack_proto_generic.c in the Linux kernel before 3.18 generates incorrect conntrack entries during handling of certain iptables rule sets for the SCTP, DCCP, GRE, and UDP-Lite protocols, which allows remote attackers to bypass intended access restrictions via packets with disallowed port numbers. | https://nvd.nist.gov/vuln/detail/CVE-2014-8160 |
1,635 | linux | 8d0207652cbe27d1f962050737848e5ad4671958 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8d0207652cbe27d1f962050737848e5ad4671958 | ->splice_write() via ->write_iter()
iter_file_splice_write() - a ->splice_write() instance that gathers the
pipe buffers, builds a bio_vec-based iov_iter covering those and feeds
it to ->write_iter(). A bunch of simple cases coverted to that...
[AV: fixed the braino spotted by Cyrill]
Signed-off-by: Al Viro <viro@z... | 1 | xfs_file_splice_write(
struct pipe_inode_info *pipe,
struct file *outfilp,
loff_t *ppos,
size_t count,
unsigned int flags)
{
struct inode *inode = outfilp->f_mapping->host;
struct xfs_inode *ip = XFS_I(inode);
int ioflags = 0;
ssize_t ret;
XFS_STATS_INC(xs_write_calls);
if (outfilp->f_mode & FMODE... | 58,931,614,698,813,260,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2014-7822 | The implementation of certain splice_write file operations in the Linux kernel before 3.16 does not enforce a restriction on the maximum size of a single file, which allows local users to cause a denial of service (system crash) or possibly have unspecified other impact via a crafted splice system call, as demonstrated... | https://nvd.nist.gov/vuln/detail/CVE-2014-7822 |
45,337 | linux | 8d0207652cbe27d1f962050737848e5ad4671958 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8d0207652cbe27d1f962050737848e5ad4671958 | ->splice_write() via ->write_iter()
iter_file_splice_write() - a ->splice_write() instance that gathers the
pipe buffers, builds a bio_vec-based iov_iter covering those and feeds
it to ->write_iter(). A bunch of simple cases coverted to that...
[AV: fixed the braino spotted by Cyrill]
Signed-off-by: Al Viro <viro@z... | 0 | xfs_file_splice_read(
struct file *infilp,
loff_t *ppos,
struct pipe_inode_info *pipe,
size_t count,
unsigned int flags)
{
struct xfs_inode *ip = XFS_I(infilp->f_mapping->host);
int ioflags = 0;
ssize_t ret;
XFS_STATS_INC(xs_read_calls);
if (infilp->f_mode & FMODE_NOCMTIME)
ioflags |= IO_INVIS;
... | 282,671,743,131,387,860,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2014-7822 | The implementation of certain splice_write file operations in the Linux kernel before 3.16 does not enforce a restriction on the maximum size of a single file, which allows local users to cause a denial of service (system crash) or possibly have unspecified other impact via a crafted splice system call, as demonstrated... | https://nvd.nist.gov/vuln/detail/CVE-2014-7822 |
1,636 | krb5 | 102bb6ebf20f9174130c85c3b052ae104e5073ec | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/102bb6ebf20f9174130c85c3b052ae104e5073ec | Fix krb5_read_message handling [CVE-2014-5355]
In recvauth_common, do not use strcmp against the data fields of
krb5_data objects populated by krb5_read_message(), as there is no
guarantee that they are C strings. Instead, create an expected
krb5_data value and use data_eq().
In the sample user-to-user server applic... | 1 | int main(argc, argv)
int argc;
char *argv[];
{
krb5_data pname_data, tkt_data;
int sock = 0;
socklen_t l;
int retval;
struct sockaddr_in l_inaddr, f_inaddr; /* local, foreign address */
krb5_creds creds, *new_creds;
krb5_ccache cc;
krb5_data msgtext, msg;
krb5_context ... | 132,886,479,854,659,200,000,000,000,000,000,000,000 | server.c | 36,266,010,581,253,480,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2014-5355 | MIT Kerberos 5 (aka krb5) through 1.13.1 incorrectly expects that a krb5_read_message data field is represented as a string ending with a '\0' character, which allows remote attackers to (1) cause a denial of service (NULL pointer dereference) via a zero-byte version string or (2) cause a denial of service (out-of-boun... | https://nvd.nist.gov/vuln/detail/CVE-2014-5355 |
159,321 | krb5 | 102bb6ebf20f9174130c85c3b052ae104e5073ec | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/102bb6ebf20f9174130c85c3b052ae104e5073ec | Fix krb5_read_message handling [CVE-2014-5355]
In recvauth_common, do not use strcmp against the data fields of
krb5_data objects populated by krb5_read_message(), as there is no
guarantee that they are C strings. Instead, create an expected
krb5_data value and use data_eq().
In the sample user-to-user server applic... | 0 | int main(argc, argv)
int argc;
char *argv[];
{
krb5_data pname_data, tkt_data;
int sock = 0;
socklen_t l;
int retval;
struct sockaddr_in l_inaddr, f_inaddr; /* local, foreign address */
krb5_creds creds, *new_creds;
krb5_ccache cc;
krb5_data msgtext, msg;
krb5_context ... | 210,953,004,867,845,740,000,000,000,000,000,000,000 | server.c | 106,639,333,056,775,080,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2014-5355 | MIT Kerberos 5 (aka krb5) through 1.13.1 incorrectly expects that a krb5_read_message data field is represented as a string ending with a '\0' character, which allows remote attackers to (1) cause a denial of service (NULL pointer dereference) via a zero-byte version string or (2) cause a denial of service (out-of-boun... | https://nvd.nist.gov/vuln/detail/CVE-2014-5355 |
9,318 | krb5 | 102bb6ebf20f9174130c85c3b052ae104e5073ec | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/102bb6ebf20f9174130c85c3b052ae104e5073ec | Fix krb5_read_message handling [CVE-2014-5355]
In recvauth_common, do not use strcmp against the data fields of
krb5_data objects populated by krb5_read_message(), as there is no
guarantee that they are C strings. Instead, create an expected
krb5_data value and use data_eq().
In the sample user-to-user server applic... | 1 | recvauth_common(krb5_context context,
krb5_auth_context * auth_context,
/* IN */
krb5_pointer fd,
char *appl_version,
krb5_principal server,
krb5_int32 flags,
krb5_keytab keytab,
/* OUT */
... | 146,562,876,660,269,340,000,000,000,000,000,000,000 | recvauth.c | 238,692,121,563,403,830,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2014-5355 | MIT Kerberos 5 (aka krb5) through 1.13.1 incorrectly expects that a krb5_read_message data field is represented as a string ending with a '\0' character, which allows remote attackers to (1) cause a denial of service (NULL pointer dereference) via a zero-byte version string or (2) cause a denial of service (out-of-boun... | https://nvd.nist.gov/vuln/detail/CVE-2014-5355 |
184,445 | krb5 | 102bb6ebf20f9174130c85c3b052ae104e5073ec | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/102bb6ebf20f9174130c85c3b052ae104e5073ec | Fix krb5_read_message handling [CVE-2014-5355]
In recvauth_common, do not use strcmp against the data fields of
krb5_data objects populated by krb5_read_message(), as there is no
guarantee that they are C strings. Instead, create an expected
krb5_data value and use data_eq().
In the sample user-to-user server applic... | 0 | recvauth_common(krb5_context context,
krb5_auth_context * auth_context,
/* IN */
krb5_pointer fd,
char *appl_version,
krb5_principal server,
krb5_int32 flags,
krb5_keytab keytab,
/* OUT */
... | 93,104,650,514,488,080,000,000,000,000,000,000,000 | recvauth.c | 8,746,267,741,222,511,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2014-5355 | MIT Kerberos 5 (aka krb5) through 1.13.1 incorrectly expects that a krb5_read_message data field is represented as a string ending with a '\0' character, which allows remote attackers to (1) cause a denial of service (NULL pointer dereference) via a zero-byte version string or (2) cause a denial of service (out-of-boun... | https://nvd.nist.gov/vuln/detail/CVE-2014-5355 |
1,656 | nbd | 741495cb08503fd32a9d22648e63b64390c601f4 | https://github.com/yoe/nbd | https://github.com/yoe/nbd/commit/741495cb08503fd32a9d22648e63b64390c601f4 | nbd-server: handle modern-style negotiation in a child process
Previously, the modern style negotiation was carried out in the root
server (listener) process before forking the actual client handler. This
made it possible for a malfunctioning or evil client to terminate the
root process simply by querying a non-existe... | 1 | void serveloop(GArray* servers) {
struct sockaddr_storage addrin;
socklen_t addrinlen=sizeof(addrin);
int i;
int max;
fd_set mset;
fd_set rset;
/*
* Set up the master fd_set. The set of descriptors we need
* to select() for never changes anyway and it buys us a *lot*
* of time to only build this once. Ho... | 143,212,735,324,855,570,000,000,000,000,000,000,000 | nbd-server.c | 174,715,315,005,731,700,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-7441 | The modern style negotiation in Network Block Device (nbd-server) 2.9.22 through 3.3 allows remote attackers to cause a denial of service (root process termination) by (1) closing the connection during negotiation or (2) specifying a name for a non-existent export. | https://nvd.nist.gov/vuln/detail/CVE-2013-7441 |
159,335 | nbd | 741495cb08503fd32a9d22648e63b64390c601f4 | https://github.com/yoe/nbd | https://github.com/yoe/nbd/commit/741495cb08503fd32a9d22648e63b64390c601f4 | nbd-server: handle modern-style negotiation in a child process
Previously, the modern style negotiation was carried out in the root
server (listener) process before forking the actual client handler. This
made it possible for a malfunctioning or evil client to terminate the
root process simply by querying a non-existe... | 0 | void serveloop(GArray* servers) {
struct sockaddr_storage addrin;
socklen_t addrinlen=sizeof(addrin);
int i;
int max;
fd_set mset;
fd_set rset;
/*
* Set up the master fd_set. The set of descriptors we need
* to select() for never changes anyway and it buys us a *lot*
* of time to only build this once. Ho... | 251,204,693,349,472,900,000,000,000,000,000,000,000 | nbd-server.c | 248,075,128,229,751,070,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-7441 | The modern style negotiation in Network Block Device (nbd-server) 2.9.22 through 3.3 allows remote attackers to cause a denial of service (root process termination) by (1) closing the connection during negotiation or (2) specifying a name for a non-existent export. | https://nvd.nist.gov/vuln/detail/CVE-2013-7441 |
1,657 | linux | 128394eff343fc6d2f32172f03e24829539c5835 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/128394eff343fc6d2f32172f03e24829539c5835 | sg_write()/bsg_write() is not fit to be called under KERNEL_DS
Both damn things interpret userland pointers embedded into the payload;
worse, they are actually traversing those. Leaving aside the bad
API design, this is very much _not_ safe to call with KERNEL_DS.
Bail out early if that happens.
Cc: stable@vger.kern... | 1 | bsg_write(struct file *file, const char __user *buf, size_t count, loff_t *ppos)
{
struct bsg_device *bd = file->private_data;
ssize_t bytes_written;
int ret;
dprintk("%s: write %Zd bytes\n", bd->name, count);
bsg_set_block(bd, file);
bytes_written = 0;
ret = __bsg_write(bd, buf, count, &bytes_written,
... | 107,643,057,290,525,440,000,000,000,000,000,000,000 | bsg.c | 6,609,762,736,419,196,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-10088 | The sg implementation in the Linux kernel through 4.9 does not properly restrict write operations in situations where the KERNEL_DS option is set, which allows local users to read or write to arbitrary kernel memory locations or cause a denial of service (use-after-free) by leveraging access to a /dev/sg device, relate... | https://nvd.nist.gov/vuln/detail/CVE-2016-10088 |
159,336 | linux | 128394eff343fc6d2f32172f03e24829539c5835 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/128394eff343fc6d2f32172f03e24829539c5835 | sg_write()/bsg_write() is not fit to be called under KERNEL_DS
Both damn things interpret userland pointers embedded into the payload;
worse, they are actually traversing those. Leaving aside the bad
API design, this is very much _not_ safe to call with KERNEL_DS.
Bail out early if that happens.
Cc: stable@vger.kern... | 0 | bsg_write(struct file *file, const char __user *buf, size_t count, loff_t *ppos)
{
struct bsg_device *bd = file->private_data;
ssize_t bytes_written;
int ret;
dprintk("%s: write %Zd bytes\n", bd->name, count);
if (unlikely(segment_eq(get_fs(), KERNEL_DS)))
return -EINVAL;
bsg_set_block(bd, file);
byt... | 299,794,038,225,016,270,000,000,000,000,000,000,000 | bsg.c | 149,960,552,629,880,700,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-10088 | The sg implementation in the Linux kernel through 4.9 does not properly restrict write operations in situations where the KERNEL_DS option is set, which allows local users to read or write to arbitrary kernel memory locations or cause a denial of service (use-after-free) by leveraging access to a /dev/sg device, relate... | https://nvd.nist.gov/vuln/detail/CVE-2016-10088 |
1,658 | linux | 128394eff343fc6d2f32172f03e24829539c5835 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/128394eff343fc6d2f32172f03e24829539c5835 | sg_write()/bsg_write() is not fit to be called under KERNEL_DS
Both damn things interpret userland pointers embedded into the payload;
worse, they are actually traversing those. Leaving aside the bad
API design, this is very much _not_ safe to call with KERNEL_DS.
Bail out early if that happens.
Cc: stable@vger.kern... | 1 | sg_write(struct file *filp, const char __user *buf, size_t count, loff_t * ppos)
{
int mxsize, cmd_size, k;
int input_size, blocking;
unsigned char opcode;
Sg_device *sdp;
Sg_fd *sfp;
Sg_request *srp;
struct sg_header old_hdr;
sg_io_hdr_t *hp;
unsigned char cmnd[SG_MAX_CDB_SIZE];
if ((!(sfp = (Sg_fd *) f... | 55,314,091,797,718,160,000,000,000,000,000,000,000 | sg.c | 199,371,262,027,085,440,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-10088 | The sg implementation in the Linux kernel through 4.9 does not properly restrict write operations in situations where the KERNEL_DS option is set, which allows local users to read or write to arbitrary kernel memory locations or cause a denial of service (use-after-free) by leveraging access to a /dev/sg device, relate... | https://nvd.nist.gov/vuln/detail/CVE-2016-10088 |
159,337 | linux | 128394eff343fc6d2f32172f03e24829539c5835 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/128394eff343fc6d2f32172f03e24829539c5835 | sg_write()/bsg_write() is not fit to be called under KERNEL_DS
Both damn things interpret userland pointers embedded into the payload;
worse, they are actually traversing those. Leaving aside the bad
API design, this is very much _not_ safe to call with KERNEL_DS.
Bail out early if that happens.
Cc: stable@vger.kern... | 0 | sg_write(struct file *filp, const char __user *buf, size_t count, loff_t * ppos)
{
int mxsize, cmd_size, k;
int input_size, blocking;
unsigned char opcode;
Sg_device *sdp;
Sg_fd *sfp;
Sg_request *srp;
struct sg_header old_hdr;
sg_io_hdr_t *hp;
unsigned char cmnd[SG_MAX_CDB_SIZE];
if (unlikely(segment_eq(g... | 228,768,404,042,677,300,000,000,000,000,000,000,000 | sg.c | 218,646,099,059,712,740,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-10088 | The sg implementation in the Linux kernel through 4.9 does not properly restrict write operations in situations where the KERNEL_DS option is set, which allows local users to read or write to arbitrary kernel memory locations or cause a denial of service (use-after-free) by leveraging access to a /dev/sg device, relate... | https://nvd.nist.gov/vuln/detail/CVE-2016-10088 |
1,659 | linux | 79dc7e3f1cd323be4c81aa1a94faa1b3ed987fb2 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/79dc7e3f1cd323be4c81aa1a94faa1b3ed987fb2 | net: handle no dst on skb in icmp6_send
Andrey reported the following while fuzzing the kernel with syzkaller:
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] SMP KASAN
Modules linked in:
CPU: 0 PID: 3859 Comm: a.out Not tainted... | 1 | static void icmp6_send(struct sk_buff *skb, u8 type, u8 code, __u32 info,
const struct in6_addr *force_saddr)
{
struct net *net = dev_net(skb->dev);
struct inet6_dev *idev = NULL;
struct ipv6hdr *hdr = ipv6_hdr(skb);
struct sock *sk;
struct ipv6_pinfo *np;
const struct in6_addr *saddr = NULL;
struct dst... | 148,411,612,446,306,800,000,000,000,000,000,000,000 | icmp.c | 303,659,297,633,054,450,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-9919 | The icmp6_send function in net/ipv6/icmp.c in the Linux kernel through 4.8.12 omits a certain check of the dst data structure, which allows remote attackers to cause a denial of service (panic) via a fragmented IPv6 packet. | https://nvd.nist.gov/vuln/detail/CVE-2016-9919 |
159,338 | linux | 79dc7e3f1cd323be4c81aa1a94faa1b3ed987fb2 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/79dc7e3f1cd323be4c81aa1a94faa1b3ed987fb2 | net: handle no dst on skb in icmp6_send
Andrey reported the following while fuzzing the kernel with syzkaller:
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] SMP KASAN
Modules linked in:
CPU: 0 PID: 3859 Comm: a.out Not tainted... | 0 | static void icmp6_send(struct sk_buff *skb, u8 type, u8 code, __u32 info,
const struct in6_addr *force_saddr)
{
struct net *net = dev_net(skb->dev);
struct inet6_dev *idev = NULL;
struct ipv6hdr *hdr = ipv6_hdr(skb);
struct sock *sk;
struct ipv6_pinfo *np;
const struct in6_addr *saddr = NULL;
struct dst... | 186,874,601,249,222,500,000,000,000,000,000,000,000 | icmp.c | 130,544,649,541,142,540,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-9919 | The icmp6_send function in net/ipv6/icmp.c in the Linux kernel through 4.8.12 omits a certain check of the dst data structure, which allows remote attackers to cause a denial of service (panic) via a fragmented IPv6 packet. | https://nvd.nist.gov/vuln/detail/CVE-2016-9919 |
1,660 | libgsf | 95a8351a75758cf10b3bf6abae0b6b461f90d9e5 | https://github.com/GNOME/libgsf | https://github.com/GNOME/libgsf/commit/95a8351a75758cf10b3bf6abae0b6b461f90d9e5 | tar: fix crash on broken tar file. | 1 | tar_directory_for_file (GsfInfileTar *dir, const char *name, gboolean last)
{
const char *s = name;
while (1) {
const char *s0 = s;
char *dirname;
/* Find a directory component, if any. */
while (1) {
if (*s == 0) {
if (last && s != s0)
break;
else
return dir;
}
/* This is delibe... | 54,320,595,055,581,590,000,000,000,000,000,000,000 | gsf-infile-tar.c | 239,316,636,556,709,400,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2016-9888 | An error within the "tar_directory_for_file()" function (gsf-infile-tar.c) in GNOME Structured File Library before 1.14.41 can be exploited to trigger a Null pointer dereference and subsequently cause a crash via a crafted TAR file. | https://nvd.nist.gov/vuln/detail/CVE-2016-9888 |
159,339 | libgsf | 95a8351a75758cf10b3bf6abae0b6b461f90d9e5 | https://github.com/GNOME/libgsf | https://github.com/GNOME/libgsf/commit/95a8351a75758cf10b3bf6abae0b6b461f90d9e5 | tar: fix crash on broken tar file. | 0 | tar_directory_for_file (GsfInfileTar *dir, const char *name, gboolean last)
{
const char *s = name;
while (1) {
const char *s0 = s;
char *dirname;
/* Find a directory component, if any. */
while (1) {
if (*s == 0) {
if (last && s != s0)
break;
else
return dir;
}
/* This is delibe... | 244,595,410,542,327,620,000,000,000,000,000,000,000 | gsf-infile-tar.c | 87,848,459,456,219,220,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2016-9888 | An error within the "tar_directory_for_file()" function (gsf-infile-tar.c) in GNOME Structured File Library before 1.14.41 can be exploited to trigger a Null pointer dereference and subsequently cause a crash via a crafted TAR file. | https://nvd.nist.gov/vuln/detail/CVE-2016-9888 |
1,661 | linux | 92964c79b357efd980812c4de5c1fd2ec8bb5520 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/92964c79b357efd980812c4de5c1fd2ec8bb5520 | netlink: Fix dump skb leak/double free
When we free cb->skb after a dump, we do it after releasing the
lock. This means that a new dump could have started in the time
being and we'll end up freeing their skb instead of ours.
This patch saves the skb and module before we unlock so we free
the right memory.
Fixes: 16... | 1 | static int netlink_dump(struct sock *sk)
{
struct netlink_sock *nlk = nlk_sk(sk);
struct netlink_callback *cb;
struct sk_buff *skb = NULL;
struct nlmsghdr *nlh;
int len, err = -ENOBUFS;
int alloc_min_size;
int alloc_size;
mutex_lock(nlk->cb_mutex);
if (!nlk->cb_running) {
err = -EINVAL;
goto errout_... | 196,001,105,598,532,200,000,000,000,000,000,000,000 | af_netlink.c | 181,510,954,759,435,270,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2016-9806 | Race condition in the netlink_dump function in net/netlink/af_netlink.c in the Linux kernel before 4.6.3 allows local users to cause a denial of service (double free) or possibly have unspecified other impact via a crafted application that makes sendmsg system calls, leading to a free operation associated with a new du... | https://nvd.nist.gov/vuln/detail/CVE-2016-9806 |
159,340 | linux | 92964c79b357efd980812c4de5c1fd2ec8bb5520 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/92964c79b357efd980812c4de5c1fd2ec8bb5520 | netlink: Fix dump skb leak/double free
When we free cb->skb after a dump, we do it after releasing the
lock. This means that a new dump could have started in the time
being and we'll end up freeing their skb instead of ours.
This patch saves the skb and module before we unlock so we free
the right memory.
Fixes: 16... | 0 | static int netlink_dump(struct sock *sk)
{
struct netlink_sock *nlk = nlk_sk(sk);
struct netlink_callback *cb;
struct sk_buff *skb = NULL;
struct nlmsghdr *nlh;
struct module *module;
int len, err = -ENOBUFS;
int alloc_min_size;
int alloc_size;
mutex_lock(nlk->cb_mutex);
if (!nlk->cb_running) {
err =... | 65,876,982,956,506,050,000,000,000,000,000,000,000 | af_netlink.c | 74,214,201,755,068,430,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2016-9806 | Race condition in the netlink_dump function in net/netlink/af_netlink.c in the Linux kernel before 4.6.3 allows local users to cause a denial of service (double free) or possibly have unspecified other impact via a crafted application that makes sendmsg system calls, leading to a free operation associated with a new du... | https://nvd.nist.gov/vuln/detail/CVE-2016-9806 |
1,662 | linux | 3aa02cb664c5fb1042958c8d1aa8c35055a2ebc4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/3aa02cb664c5fb1042958c8d1aa8c35055a2ebc4 | ALSA: pcm : Call kill_fasync() in stream lock
Currently kill_fasync() is called outside the stream lock in
snd_pcm_period_elapsed(). This is potentially racy, since the stream
may get released even during the irq handler is running. Although
snd_pcm_release_substream() calls snd_pcm_drop(), this doesn't
guarantee th... | 1 | void snd_pcm_period_elapsed(struct snd_pcm_substream *substream)
{
struct snd_pcm_runtime *runtime;
unsigned long flags;
if (PCM_RUNTIME_CHECK(substream))
return;
runtime = substream->runtime;
snd_pcm_stream_lock_irqsave(substream, flags);
if (!snd_pcm_running(substream) ||
snd_pcm_update_hw_ptr0(substre... | 161,224,995,451,594,300,000,000,000,000,000,000,000 | pcm_lib.c | 125,569,751,360,658,480,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-9794 | Race condition in the snd_pcm_period_elapsed function in sound/core/pcm_lib.c in the ALSA subsystem in the Linux kernel before 4.7 allows local users to cause a denial of service (use-after-free) or possibly have unspecified other impact via a crafted SNDRV_PCM_TRIGGER_START command. | https://nvd.nist.gov/vuln/detail/CVE-2016-9794 |
159,341 | linux | 3aa02cb664c5fb1042958c8d1aa8c35055a2ebc4 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/3aa02cb664c5fb1042958c8d1aa8c35055a2ebc4 | ALSA: pcm : Call kill_fasync() in stream lock
Currently kill_fasync() is called outside the stream lock in
snd_pcm_period_elapsed(). This is potentially racy, since the stream
may get released even during the irq handler is running. Although
snd_pcm_release_substream() calls snd_pcm_drop(), this doesn't
guarantee th... | 0 | void snd_pcm_period_elapsed(struct snd_pcm_substream *substream)
{
struct snd_pcm_runtime *runtime;
unsigned long flags;
if (PCM_RUNTIME_CHECK(substream))
return;
runtime = substream->runtime;
snd_pcm_stream_lock_irqsave(substream, flags);
if (!snd_pcm_running(substream) ||
snd_pcm_update_hw_ptr0(substre... | 95,192,394,536,213,600,000,000,000,000,000,000,000 | pcm_lib.c | 176,132,187,734,148,700,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-9794 | Race condition in the snd_pcm_period_elapsed function in sound/core/pcm_lib.c in the ALSA subsystem in the Linux kernel before 4.7 allows local users to cause a denial of service (use-after-free) or possibly have unspecified other impact via a crafted SNDRV_PCM_TRIGGER_START command. | https://nvd.nist.gov/vuln/detail/CVE-2016-9794 |
1,663 | linux | b98b0bc8c431e3ceb4b26b0dfc8db509518fb290 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b98b0bc8c431e3ceb4b26b0dfc8db509518fb290 | net: avoid signed overflows for SO_{SND|RCV}BUFFORCE
CAP_NET_ADMIN users should not be allowed to set negative
sk_sndbuf or sk_rcvbuf values, as it can lead to various memory
corruptions, crashes, OOM...
Note that before commit 82981930125a ("net: cleanups in
sock_setsockopt()"), the bug was even more serious, since ... | 1 | int sock_setsockopt(struct socket *sock, int level, int optname,
char __user *optval, unsigned int optlen)
{
struct sock *sk = sock->sk;
int val;
int valbool;
struct linger ling;
int ret = 0;
/*
* Options without arguments
*/
if (optname == SO_BINDTODEVICE)
return sock_setbindtodevice(sk, optval, o... | 66,744,804,628,888,285,000,000,000,000,000,000,000 | sock.c | 37,494,279,310,679,760,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-9793 | The sock_setsockopt function in net/core/sock.c in the Linux kernel before 4.8.14 mishandles negative values of sk_sndbuf and sk_rcvbuf, which allows local users to cause a denial of service (memory corruption and system crash) or possibly have unspecified other impact by leveraging the CAP_NET_ADMIN capability for a c... | https://nvd.nist.gov/vuln/detail/CVE-2016-9793 |
159,342 | linux | b98b0bc8c431e3ceb4b26b0dfc8db509518fb290 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b98b0bc8c431e3ceb4b26b0dfc8db509518fb290 | net: avoid signed overflows for SO_{SND|RCV}BUFFORCE
CAP_NET_ADMIN users should not be allowed to set negative
sk_sndbuf or sk_rcvbuf values, as it can lead to various memory
corruptions, crashes, OOM...
Note that before commit 82981930125a ("net: cleanups in
sock_setsockopt()"), the bug was even more serious, since ... | 0 | int sock_setsockopt(struct socket *sock, int level, int optname,
char __user *optval, unsigned int optlen)
{
struct sock *sk = sock->sk;
int val;
int valbool;
struct linger ling;
int ret = 0;
/*
* Options without arguments
*/
if (optname == SO_BINDTODEVICE)
return sock_setbindtodevice(sk, optval, o... | 66,960,051,526,910,360,000,000,000,000,000,000,000 | sock.c | 172,104,193,569,168,170,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-9793 | The sock_setsockopt function in net/core/sock.c in the Linux kernel before 4.8.14 mishandles negative values of sk_sndbuf and sk_rcvbuf, which allows local users to cause a denial of service (memory corruption and system crash) or possibly have unspecified other impact by leveraging the CAP_NET_ADMIN capability for a c... | https://nvd.nist.gov/vuln/detail/CVE-2016-9793 |
1,664 | linux | 81cdb259fb6d8c1c4ecfeea389ff5a73c07f5755 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/81cdb259fb6d8c1c4ecfeea389ff5a73c07f5755 | KVM: x86: fix out-of-bounds accesses of rtc_eoi map
KVM was using arrays of size KVM_MAX_VCPUS with vcpu_id, but ID can be
bigger that the maximal number of VCPUs, resulting in out-of-bounds
access.
Found by syzkaller:
BUG: KASAN: slab-out-of-bounds in __apic_accept_irq+0xb33/0xb50 at addr [...]
Write of size 1 ... | 1 | static void rtc_irq_eoi_tracking_reset(struct kvm_ioapic *ioapic)
{
ioapic->rtc_status.pending_eoi = 0;
bitmap_zero(ioapic->rtc_status.dest_map.map, KVM_MAX_VCPUS);
}
| 131,623,410,041,848,010,000,000,000,000,000,000,000 | ioapic.c | 261,284,608,400,710,700,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2016-9777 | KVM in the Linux kernel before 4.8.12, when I/O APIC is enabled, does not properly restrict the VCPU index, which allows guest OS users to gain host OS privileges or cause a denial of service (out-of-bounds array access and host OS crash) via a crafted interrupt request, related to arch/x86/kvm/ioapic.c and arch/x86/kv... | https://nvd.nist.gov/vuln/detail/CVE-2016-9777 |
159,343 | linux | 81cdb259fb6d8c1c4ecfeea389ff5a73c07f5755 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/81cdb259fb6d8c1c4ecfeea389ff5a73c07f5755 | KVM: x86: fix out-of-bounds accesses of rtc_eoi map
KVM was using arrays of size KVM_MAX_VCPUS with vcpu_id, but ID can be
bigger that the maximal number of VCPUs, resulting in out-of-bounds
access.
Found by syzkaller:
BUG: KASAN: slab-out-of-bounds in __apic_accept_irq+0xb33/0xb50 at addr [...]
Write of size 1 ... | 0 | static void rtc_irq_eoi_tracking_reset(struct kvm_ioapic *ioapic)
{
ioapic->rtc_status.pending_eoi = 0;
bitmap_zero(ioapic->rtc_status.dest_map.map, KVM_MAX_VCPU_ID);
}
| 256,233,545,067,978,100,000,000,000,000,000,000,000 | ioapic.c | 40,431,863,322,526,423,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2016-9777 | KVM in the Linux kernel before 4.8.12, when I/O APIC is enabled, does not properly restrict the VCPU index, which allows guest OS users to gain host OS privileges or cause a denial of service (out-of-bounds array access and host OS crash) via a crafted interrupt request, related to arch/x86/kvm/ioapic.c and arch/x86/kv... | https://nvd.nist.gov/vuln/detail/CVE-2016-9777 |
1,667 | linux | 9b57da0630c9fd36ed7a20fc0f98dc82cc0777fa | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b57da0630c9fd36ed7a20fc0f98dc82cc0777fa | netfilter: ipv6: nf_defrag: drop mangled skb on ream error
Dmitry Vyukov reported GPF in network stack that Andrey traced down to
negative nh offset in nf_ct_frag6_queue().
Problem is that all network headers before fragment header are pulled.
Normal ipv6 reassembly will drop the skb when errors occur further down
th... | 1 | int nf_ct_frag6_gather(struct net *net, struct sk_buff *skb, u32 user)
{
struct net_device *dev = skb->dev;
int fhoff, nhoff, ret;
struct frag_hdr *fhdr;
struct frag_queue *fq;
struct ipv6hdr *hdr;
u8 prevhdr;
/* Jumbo payload inhibits frag. header */
if (ipv6_hdr(skb)->payload_len == 0) {
pr_debug("paylo... | 162,173,779,084,684,320,000,000,000,000,000,000,000 | nf_conntrack_reasm.c | 248,081,613,101,425,030,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2016-9755 | The netfilter subsystem in the Linux kernel before 4.9 mishandles IPv6 reassembly, which allows local users to cause a denial of service (integer overflow, out-of-bounds write, and GPF) or possibly have unspecified other impact via a crafted application that makes socket, connect, and writev system calls, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2016-9755 |
159,344 | linux | 9b57da0630c9fd36ed7a20fc0f98dc82cc0777fa | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b57da0630c9fd36ed7a20fc0f98dc82cc0777fa | netfilter: ipv6: nf_defrag: drop mangled skb on ream error
Dmitry Vyukov reported GPF in network stack that Andrey traced down to
negative nh offset in nf_ct_frag6_queue().
Problem is that all network headers before fragment header are pulled.
Normal ipv6 reassembly will drop the skb when errors occur further down
th... | 0 | int nf_ct_frag6_gather(struct net *net, struct sk_buff *skb, u32 user)
{
struct net_device *dev = skb->dev;
int fhoff, nhoff, ret;
struct frag_hdr *fhdr;
struct frag_queue *fq;
struct ipv6hdr *hdr;
u8 prevhdr;
/* Jumbo payload inhibits frag. header */
if (ipv6_hdr(skb)->payload_len == 0) {
pr_debug("paylo... | 25,949,360,988,672,850,000,000,000,000,000,000,000 | nf_conntrack_reasm.c | 181,665,345,411,147,200,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2016-9755 | The netfilter subsystem in the Linux kernel before 4.9 mishandles IPv6 reassembly, which allows local users to cause a denial of service (integer overflow, out-of-bounds write, and GPF) or possibly have unspecified other impact via a crafted application that makes socket, connect, and writev system calls, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2016-9755 |
1,668 | linux | 9b57da0630c9fd36ed7a20fc0f98dc82cc0777fa | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b57da0630c9fd36ed7a20fc0f98dc82cc0777fa | netfilter: ipv6: nf_defrag: drop mangled skb on ream error
Dmitry Vyukov reported GPF in network stack that Andrey traced down to
negative nh offset in nf_ct_frag6_queue().
Problem is that all network headers before fragment header are pulled.
Normal ipv6 reassembly will drop the skb when errors occur further down
th... | 1 | static unsigned int ipv6_defrag(void *priv,
struct sk_buff *skb,
const struct nf_hook_state *state)
{
int err;
#if IS_ENABLED(CONFIG_NF_CONNTRACK)
/* Previously seen (loopback)? */
if (skb->nfct && !nf_ct_is_template((struct nf_conn *)skb->nfct))
return NF_ACCEPT;
#endif
err = nf_ct_frag6_gather(state->... | 58,843,208,546,829,070,000,000,000,000,000,000,000 | nf_defrag_ipv6_hooks.c | 263,801,013,687,032,600,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2016-9755 | The netfilter subsystem in the Linux kernel before 4.9 mishandles IPv6 reassembly, which allows local users to cause a denial of service (integer overflow, out-of-bounds write, and GPF) or possibly have unspecified other impact via a crafted application that makes socket, connect, and writev system calls, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2016-9755 |
159,345 | linux | 9b57da0630c9fd36ed7a20fc0f98dc82cc0777fa | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9b57da0630c9fd36ed7a20fc0f98dc82cc0777fa | netfilter: ipv6: nf_defrag: drop mangled skb on ream error
Dmitry Vyukov reported GPF in network stack that Andrey traced down to
negative nh offset in nf_ct_frag6_queue().
Problem is that all network headers before fragment header are pulled.
Normal ipv6 reassembly will drop the skb when errors occur further down
th... | 0 | static unsigned int ipv6_defrag(void *priv,
struct sk_buff *skb,
const struct nf_hook_state *state)
{
int err;
#if IS_ENABLED(CONFIG_NF_CONNTRACK)
/* Previously seen (loopback)? */
if (skb->nfct && !nf_ct_is_template((struct nf_conn *)skb->nfct))
return NF_ACCEPT;
#endif
err = nf_ct_frag6_gather(state->... | 335,300,449,153,716,800,000,000,000,000,000,000,000 | nf_defrag_ipv6_hooks.c | 216,353,031,272,739,450,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2016-9755 | The netfilter subsystem in the Linux kernel before 4.9 mishandles IPv6 reassembly, which allows local users to cause a denial of service (integer overflow, out-of-bounds write, and GPF) or possibly have unspecified other impact via a crafted application that makes socket, connect, and writev system calls, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2016-9755 |
1,675 | linux | a0ac402cfcdc904f9772e1762b3fda112dcc56a0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a0ac402cfcdc904f9772e1762b3fda112dcc56a0 | Don't feed anything but regular iovec's to blk_rq_map_user_iov
In theory we could map other things, but there's a reason that function
is called "user_iov". Using anything else (like splice can do) just
confuses it.
Reported-and-tested-by: Johannes Thumshirn <jthumshirn@suse.de>
Cc: Al Viro <viro@ZenIV.linux.org.uk>... | 1 | int blk_rq_map_user_iov(struct request_queue *q, struct request *rq,
struct rq_map_data *map_data,
const struct iov_iter *iter, gfp_t gfp_mask)
{
bool copy = false;
unsigned long align = q->dma_pad_mask | queue_dma_alignment(q);
struct bio *bio = NULL;
struct iov_iter i;
int ret;
if (map_data)
copy ... | 26,597,385,003,267,720,000,000,000,000,000,000,000 | blk-map.c | 40,067,109,018,686,807,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-9576 | The blk_rq_map_user_iov function in block/blk-map.c in the Linux kernel before 4.8.14 does not properly restrict the type of iterator, which allows local users to read or write to arbitrary kernel memory locations or cause a denial of service (use-after-free) by leveraging access to a /dev/sg device. | https://nvd.nist.gov/vuln/detail/CVE-2016-9576 |
159,352 | linux | a0ac402cfcdc904f9772e1762b3fda112dcc56a0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a0ac402cfcdc904f9772e1762b3fda112dcc56a0 | Don't feed anything but regular iovec's to blk_rq_map_user_iov
In theory we could map other things, but there's a reason that function
is called "user_iov". Using anything else (like splice can do) just
confuses it.
Reported-and-tested-by: Johannes Thumshirn <jthumshirn@suse.de>
Cc: Al Viro <viro@ZenIV.linux.org.uk>... | 0 | int blk_rq_map_user_iov(struct request_queue *q, struct request *rq,
struct rq_map_data *map_data,
const struct iov_iter *iter, gfp_t gfp_mask)
{
bool copy = false;
unsigned long align = q->dma_pad_mask | queue_dma_alignment(q);
struct bio *bio = NULL;
struct iov_iter i;
int ret;
if (!iter_is_iovec(iter... | 335,912,908,018,635,300,000,000,000,000,000,000,000 | blk-map.c | 85,151,335,798,775,690,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-9576 | The blk_rq_map_user_iov function in block/blk-map.c in the Linux kernel before 4.8.14 does not properly restrict the type of iterator, which allows local users to read or write to arbitrary kernel memory locations or cause a denial of service (use-after-free) by leveraging access to a /dev/sg device. | https://nvd.nist.gov/vuln/detail/CVE-2016-9576 |
1,678 | libtiff | ae9365db1b271b62b35ce018eac8799b1d5e8a53 | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/ae9365db1b271b62b35ce018eac8799b1d5e8a53 | * tools/tiffcrop.c: fix out-of-bound read of up to 3 bytes in
readContigTilesIntoBuffer(). Reported as MSVR 35092 by Axel Souchet
& Vishal Chauhan from the MSRC Vulnerabilities & Mitigations team. | 1 | static int readContigTilesIntoBuffer (TIFF* in, uint8* buf,
uint32 imagelength,
uint32 imagewidth,
uint32 tw, uint32 tl,
tsample_t spp, uint16 bps)
{
int status ... | 246,301,533,722,000,940,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2016-9539 | tools/tiffcrop.c in libtiff 4.0.6 has an out-of-bounds read in readContigTilesIntoBuffer(). Reported as MSVR 35092. | https://nvd.nist.gov/vuln/detail/CVE-2016-9539 |
159,353 | libtiff | ae9365db1b271b62b35ce018eac8799b1d5e8a53 | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/ae9365db1b271b62b35ce018eac8799b1d5e8a53 | * tools/tiffcrop.c: fix out-of-bound read of up to 3 bytes in
readContigTilesIntoBuffer(). Reported as MSVR 35092 by Axel Souchet
& Vishal Chauhan from the MSRC Vulnerabilities & Mitigations team. | 0 | static int readContigTilesIntoBuffer (TIFF* in, uint8* buf,
uint32 imagelength,
uint32 imagewidth,
uint32 tw, uint32 tl,
tsample_t spp, uint16 bps)
{
int status ... | 148,839,310,386,144,290,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2016-9539 | tools/tiffcrop.c in libtiff 4.0.6 has an out-of-bounds read in readContigTilesIntoBuffer(). Reported as MSVR 35092. | https://nvd.nist.gov/vuln/detail/CVE-2016-9539 |
1,704 | w3m | d43527cfa0dbb3ccefec4a6f7b32c1434739aa29 | https://github.com/tats/w3m | https://github.com/tats/w3m/commit/d43527cfa0dbb3ccefec4a6f7b32c1434739aa29 | Merge pull request #27 from kcwu/fix-strgrow
Fix potential heap buffer corruption due to Strgrow | 1 | Strgrow(Str x)
{
char *old = x->ptr;
int newlen;
newlen = x->length * 6 / 5;
if (newlen == x->length)
newlen += 2;
x->ptr = GC_MALLOC_ATOMIC(newlen);
x->area_size = newlen;
bcopy((void *)old, (void *)x->ptr, x->length);
GC_free(old);
}
| 127,289,135,144,358,380,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-9442 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31. w3m allows remote attackers to cause memory corruption in certain conditions via a crafted HTML page. | https://nvd.nist.gov/vuln/detail/CVE-2016-9442 |
159,356 | w3m | d43527cfa0dbb3ccefec4a6f7b32c1434739aa29 | https://github.com/tats/w3m | https://github.com/tats/w3m/commit/d43527cfa0dbb3ccefec4a6f7b32c1434739aa29 | Merge pull request #27 from kcwu/fix-strgrow
Fix potential heap buffer corruption due to Strgrow | 0 | Strgrow(Str x)
{
char *old = x->ptr;
int newlen;
newlen = x->area_size * 6 / 5;
if (newlen == x->area_size)
newlen += 2;
x->ptr = GC_MALLOC_ATOMIC(newlen);
x->area_size = newlen;
bcopy((void *)old, (void *)x->ptr, x->length);
GC_free(old);
}
| 279,932,231,335,318,980,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-9442 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31. w3m allows remote attackers to cause memory corruption in certain conditions via a crafted HTML page. | https://nvd.nist.gov/vuln/detail/CVE-2016-9442 |
1,706 | linux | 93362fa47fe98b62e4a34ab408c4a418432e7939 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/93362fa47fe98b62e4a34ab408c4a418432e7939 | sysctl: Drop reference added by grab_header in proc_sys_readdir
Fixes CVE-2016-9191, proc_sys_readdir doesn't drop reference
added by grab_header when return from !dir_emit_dots path.
It can cause any path called unregister_sysctl_table will
wait forever.
The calltrace of CVE-2016-9191:
[ 5535.960522] Call Trace:
[ ... | 1 | static int proc_sys_readdir(struct file *file, struct dir_context *ctx)
{
struct ctl_table_header *head = grab_header(file_inode(file));
struct ctl_table_header *h = NULL;
struct ctl_table *entry;
struct ctl_dir *ctl_dir;
unsigned long pos;
if (IS_ERR(head))
return PTR_ERR(head);
ctl_dir = container_of(head... | 225,602,089,609,046,580,000,000,000,000,000,000,000 | proc_sysctl.c | 174,833,638,602,164,460,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-9191 | The cgroup offline implementation in the Linux kernel through 4.8.11 mishandles certain drain operations, which allows local users to cause a denial of service (system hang) by leveraging access to a container environment for executing a crafted application, as demonstrated by trinity. | https://nvd.nist.gov/vuln/detail/CVE-2016-9191 |
159,358 | linux | 93362fa47fe98b62e4a34ab408c4a418432e7939 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/93362fa47fe98b62e4a34ab408c4a418432e7939 | sysctl: Drop reference added by grab_header in proc_sys_readdir
Fixes CVE-2016-9191, proc_sys_readdir doesn't drop reference
added by grab_header when return from !dir_emit_dots path.
It can cause any path called unregister_sysctl_table will
wait forever.
The calltrace of CVE-2016-9191:
[ 5535.960522] Call Trace:
[ ... | 0 | static int proc_sys_readdir(struct file *file, struct dir_context *ctx)
{
struct ctl_table_header *head = grab_header(file_inode(file));
struct ctl_table_header *h = NULL;
struct ctl_table *entry;
struct ctl_dir *ctl_dir;
unsigned long pos;
if (IS_ERR(head))
return PTR_ERR(head);
ctl_dir = container_of(head... | 239,228,216,174,386,660,000,000,000,000,000,000,000 | proc_sysctl.c | 258,139,468,880,634,350,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-9191 | The cgroup offline implementation in the Linux kernel through 4.8.11 mishandles certain drain operations, which allows local users to cause a denial of service (system hang) by leveraging access to a container environment for executing a crafted application, as demonstrated by trinity. | https://nvd.nist.gov/vuln/detail/CVE-2016-9191 |
1,710 | linux | 9590232bb4f4cc824f3425a6e1349afbe6d6d2b7 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9590232bb4f4cc824f3425a6e1349afbe6d6d2b7 | staging/android/ion : fix a race condition in the ion driver
There is a use-after-free problem in the ion driver.
This is caused by a race condition in the ion_ioctl()
function.
A handle has ref count of 1 and two tasks on different
cpus calls ION_IOC_FREE simultaneously.
cpu 0 cpu ... | 1 | static long ion_ioctl(struct file *filp, unsigned int cmd, unsigned long arg)
{
struct ion_client *client = filp->private_data;
struct ion_device *dev = client->dev;
struct ion_handle *cleanup_handle = NULL;
int ret = 0;
unsigned int dir;
union {
struct ion_fd_data fd;
struct ion_allocation_data allocation;
... | 33,118,785,611,393,110,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2016-9120 | Race condition in the ion_ioctl function in drivers/staging/android/ion/ion.c in the Linux kernel before 4.6 allows local users to gain privileges or cause a denial of service (use-after-free) by calling ION_IOC_FREE on two CPUs at the same time. | https://nvd.nist.gov/vuln/detail/CVE-2016-9120 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.